| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, pgsql-committers <pgsql-committers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] pgsql: Avoid archiving XLOG_RUNNING_XACTS on idle server |
| Date: | 2016-04-06 08:45:34 |
| Message-ID: | 20160406084534.v4g7iey2iqlyy57r@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 2016-04-06 09:18:54 +0100, Simon Riggs wrote:
> Rather than take that option, I went to the trouble of writing a patch that
> does the same thing but simpler, less invasive and more maintainable.
> Primarily, I did that for you, to avoid you having wasted your time and to
> allow you to backpatch a solution.
But it doesn't. It doesn't solve the longstanding problem of checkpoints
needlessly being repeated due to standby snapshots. It doesn't fix the
issue for for wal_level=logical. We now log more WAL with
XLogArchiveTimeout > 0 than without.
The other was an architectural fix, this is a selectively applied
bandaid.
Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2016-04-06 09:04:42 | Re: [COMMITTERS] pgsql: Avoid archiving XLOG_RUNNING_XACTS on idle server |
| Previous Message | Fujii Masao | 2016-04-06 08:21:33 | pgsql: Support multiple synchronous standby servers. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2016-04-06 09:04:42 | Re: [COMMITTERS] pgsql: Avoid archiving XLOG_RUNNING_XACTS on idle server |
| Previous Message | Fujii Masao | 2016-04-06 08:23:39 | Re: Support for N synchronous standby servers - take 2 |