| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Remove secondary checkpoint |
| Date: | 2017-10-24 13:55:35 |
| Message-ID: | 20171024135535.3dk2txzriyepalmc@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2017-10-24 09:50:12 -0400, Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> > Remove the code that maintained two checkpoint's WAL files and all
> > associated stuff.
>
> > Try to avoid breaking anything else
>
> > This
> > * reduces disk space requirements on master
> > * removes a minor bug in fast failover
> > * simplifies code
>
> Doesn't it also make crash recovery less robust?
I think it does the contrary. The current mechanism is, in my opinion,
downright dangerous:
https://www.postgresql.org/message-id/20160201235854.GO8743@awork2.anarazel.de
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-10-24 14:09:09 | Re: Current int & float overflow checking is slow. |
| Previous Message | Gaddam Sai Ram | 2017-10-24 13:54:19 | Help needed regarding DSA based in-memory index! |