| From: | Pankaj Mishra <pankaj(dot)mimit(at)gmail(dot)com> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pg_xlog is getting bigger |
| Date: | 2013-11-25 09:30:56 |
| Message-ID: | CADgijrguDpk_Xg=XBeH2mNHtOYLJvz=QGmchT4xx1de+sg4epQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Dera Kevin,
If you run checkpoint in database then you can delete the pg_xlog other
then current timestamp. We do this to our customer on regular basis when
pg_xlog exceed more then 15 gb
Regards
Pankaj
On Sat, Nov 23, 2013 at 1:48 AM, Kevin Grittner <kgrittn(at)ymail(dot)com> wrote:
> Pankaj <pankaj(dot)mimit(at)gmail(dot)com> wrote:
>
> > now go to pg_xlog folder you can can see a pattern in file names of logs.
> > Just remove the file other then current time stamp. Or for safety remove
> > logs other then current date.
>
> No!!! NEVER remove ANY files from the pg_xlog sub-directory! That
> will corrupt your database.
>
> --
> Kevin Grittner
> EDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | 邓尧 | 2013-11-25 09:33:51 | Weird "function does not exist" error. |
| Previous Message | slapo | 2013-11-25 09:19:03 | Re: [GENERAL] Puzzling table scan in a CTE |