It is customary to inline or bottom-posts on these lists. Please follow the example of those responding to your emails.
On Mon, Feb 27, 2017 at 6:45 PM, Sasa Vilic <sasavi...@gmail.com> wrote: > And also this: > > """ > If archive_mode is set to on, the archiver is not enabled during recovery > or standby mode. If the standby server is promoted, it will start archiving > after the promotion, but will not archive any WAL it did not generate > itself. To get a complete series of WAL files in the archive, you must > ensure that all WAL is archived, before it reaches the standby > """ > > If I understand it correctly, WAL started on master but finished on > standby (after failover) will still not be (old master is presumably dead > and new master must wait for next WAL segment). Of course, the next WAL > segment will be sent by new master, but we are going to miss exactly this > one WAL segment during which failover occurred and thus introduce > interruption in our WAL stream. Am I right? > Requires knowledge and familiarity I present lack. Sorry. I think I see where you are going with all of this but it would probably help to explicitly state the overall concern or plan and not just ask how specific mechanics work in isolation. David J.
