Re: BUG #14109: pg_rewind fails to update target control file in one scenario
От | John Lumby |
---|---|
Тема | Re: BUG #14109: pg_rewind fails to update target control file in one scenario |
Дата | |
Msg-id | COL131-W383FA65CC9B62A7ED0157DA3620@phx.gbl обсуждение исходный текст |
Ответ на | Re: BUG #14109: pg_rewind fails to update target control file in one scenario (Julien Rouhaud <julien.rouhaud@dalibo.com>) |
Ответы |
Re: BUG #14109: pg_rewind fails to update target control file
in one scenario
|
Список | pgsql-bugs |
I've tested same scenario but with the setting=0A= =0A= recovery_target_timeline =3D 'latest'=0A= =0A= and on 9.5.2=2C=0A= =0A= and now the new Standby receives new WAL correctly after the pg_rewind and = restart=0A= =0A= So=2C=A0 assuming this is reliable (will work without requiring archiving)= =0A= then my problem is solved.=0A= =0A= Thanks for everyone's help=2C=A0 please close the bug as user error=0A= =0A= Cheers=2C=A0 John=0A= =0A= ----------------------------------------=0A= > Subject: Re: [BUGS] BUG #14109: pg_rewind fails to update target control = file in one scenario=0A= > To: johnlumby@hotmail.com=3B michael.paquier@gmail.com=0A= > CC: pgsql-bugs@postgresql.org=0A= > From: julien.rouhaud@dalibo.com=0A= > Date: Mon=2C 25 Apr 2016 19:06:57 +0200=0A= >=0A= > On 25/04/2016 17:45=2C John Lumby wrote:=0A= >>> From: julien.rouhaud@dalibo.com=0A= >>>=0A= >>> Did you set the recovery_target_timeline parameter to "latest" in the= =0A= >>> recovery.conf file? (see=0A= >>> http://www.postgresql.org/docs/current/static/recovery-target-settings.= html).=0A= >>=0A= >> Thanks Julien=2C no I did not=2C I will re-test with that later=2C on 9.= 5.2=0A= >> Meanwhile one question on that. The documentation states=0A= >> "Setting this to latest recovers=0A= >> to the latest timeline found in the archive=2C which ..."=0A= >> However I am running my systems with=0A= >> archive_mode =3D off=0A= >> I am wondering whether=0A= >> recovery_target_timeline parameter =3D "latest"=0A= >> is expected to work reliably to fix my particular problem when archiving= is not in effect.=0A= >>=0A= >=0A= > I'm not sure where it's documented=2C but the timeline change works with= =0A= > log shipping=2C and since 9.3 with streaming replication.=0A= >=0A= > That's why Michael previously said: "System A is still on its previous=0A= > timeline 11=2C and will jump=0A= > to timeline 12 once it has connected back. That's possible since 9.3."=0A= >=0A= > --=0A= > Julien Rouhaud=0A= > http://dalibo.com - http://dalibo.org=0A= =
В списке pgsql-bugs по дате отправления: