From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_rewind test race condition..? |
Date: | 2016-03-26 12:27:29 |
Message-ID: | CAB7nPqQCbLrmd=nGj1ozs+bUbFjZqkXHHXAhEzLE0NiGsbj_fg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Apr 29, 2015 at 10:03 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> Another thought would be to provide an option to pg_rewind to have it do
> an explicit checkpoint before it reads the control file.. I'm not
> against having it simply always do it as I don't see pg_rewind being a
> commonly run thing, but I know some environments have very heavy
> checkpoints and that might not be ideal.
Waking an old thread. It seems to me that such an option would still
be useful when rewinding using a stream so as an inconsistent control
file is not read. The default should definitely be to not issue this
checkpoint, but in some environments I believe that this could really
matter, say two failovers followed by two rewinds done consequently.
Thoughts?
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2016-03-26 12:37:19 | Re: Alter or rename enum value |
Previous Message | David Rowley | 2016-03-26 11:55:35 | Re: Can we amend gitignore so git postgresql works with git on windows using Msys/Mingw64 |