From: | Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com> |
---|---|
To: | Samir Magar <samirmagar8(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Delay in converting logs from ready state to done state |
Date: | 2016-10-12 06:03:53 |
Message-ID: | ec7967ee-10bb-d0fc-e27d-a0e2200652c9@dalibo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 12/10/2016 07:26, Samir Magar wrote:
> Team,
>
> we are seeing delay in converting logs from ready state to done state in
> pg_xlog archive status.
>
> we have seen pg_xlog generated 2000 per hour and it is getting archived
> 1894. So the speed at which the archiving is done is too slow as compare
> to the pg_xlog generation
>
> So our pg_xlog directory keeps filling regularly. What should be the
> real cause here?
>
> We cannot see any specific error on pg_log except no space left on device.
>
>
>
> current setting:
>
> wal_level = archive
>
> archive_mode = on
>
> max_wal_senders = 3
>
> archive_command = 'gzip < %p > /pgarchive/%f'
>
You could use pigz which is parallel, that could speed up compression.
> checkpoint_segments = 3
>
this is way to low. If you generate 2000 WAL per hour, you should
configure it to something like 170 (or 5 min average if 2000 is a
spike). It'll perform less checkpoint and also generate less WALs.
--
Julien Rouhaud
http://dalibo.com - http://dalibo.org
From | Date | Subject | |
---|---|---|---|
Next Message | Samir Magar | 2016-10-12 07:04:35 | Fwd: Delay in converting logs from ready state to done state |
Previous Message | Samir Magar | 2016-10-12 05:26:38 | Delay in converting logs from ready state to done state |