From: | Raghu Ram <raghuchennuru(at)gmail(dot)com> |
---|---|
To: | Marcello Lorenzi <mlorenzi(at)sorint(dot)it> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Postgres 9.2 pg_xlog cleanup |
Date: | 2013-11-27 16:25:25 |
Message-ID: | CALnrrJQE0eUvf-5Rg8nkFtWXS1rspYRyCqGvN44xM4OdNJotwQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Wed, Nov 27, 2013 at 9:27 PM, Marcello Lorenzi <mlorenzi(at)sorint(dot)it>wrote:
> Hi All,
> I'm installing a new Postgres 9.2 instance on my test environment and I
> noticed that the pg_xlog directory use a lot of space. I already configured
> the WAL but not the archiving for this datsa. Is it possible to implement a
> retention on pg_xlog data files?
>
>
WAL buffers holds the changes made to the database in the transaction
logs(pg_xlogs), in order to guarantee transaction security. When a
transaction commits,all transaction records are stored in to disk/permanent
storage i.e Pg_xlog directory.
I would request to monitor database server log file located under "pg_log"
directory,may be archive command failing due to that .ready files are
increasing under ../pg_xlog/archive_status directory and occupying more
space. If you fix the archive command issues,then everything will comes
under control.
Thanks & Regards
Raghu Ram
From | Date | Subject | |
---|---|---|---|
Next Message | Ray Stell | 2013-11-27 21:05:47 | Re: Postgres 9.2 pg_xlog cleanup |
Previous Message | Marcello Lorenzi | 2013-11-27 15:57:45 | Postgres 9.2 pg_xlog cleanup |