| From: | Stuart Bishop <stuart(at)stuartbishop(dot)net> |
|---|---|
| To: | Mike Wilson <mfwilson(at)gmail(dot)com> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Replication Lag Causes |
| Date: | 2014-11-04 12:34:24 |
| Message-ID: | CADmi=6N-eML3_XWBKKhBo7zhnjcmY3UT5ZBY6Za+b9UCGA3fcA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 2 November 2014 05:33, Mike Wilson <mfwilson(at)gmail(dot)com> wrote:
> Any recommendations would be very helpful.
Try using ionice and renice to increase the priority of the WAL sender
process on the master. If it helps, you are lagging because not enough
resources are being used by the sender process (rather than the slave
having trouble, for example). Lowering the number of concurrent
connections in your pgbouncer connection pool could help here.
--
Stuart Bishop <stuart(at)stuartbishop(dot)net>
http://www.stuartbishop.net/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2014-11-04 16:02:26 | Re: unnecessary sort in the execution plan when doing group by |
| Previous Message | Andrew Dunstan | 2014-11-03 20:31:16 | Re: assignment vs SELECT INTO |