Re: hot_standby_feedback and max_standby_archive_delay
От | Fujii Masao |
---|---|
Тема | Re: hot_standby_feedback and max_standby_archive_delay |
Дата | |
Msg-id | CAHGQGwFnnw0sBYh6=osF7_A+uTyUC5=-56hrJv6jvYb=C4hhbQ@mail.gmail.com обсуждение исходный текст |
Ответ на | hot_standby_feedback and max_standby_archive_delay (Marko Tiikkaja <marko@joh.to>) |
Ответы |
Re: hot_standby_feedback and max_standby_archive_delay
|
Список | pgsql-docs |
On Fri, Jan 17, 2014 at 8:38 AM, Marko Tiikkaja <marko@joh.to> wrote: > Hi, > > Myself and others found this statement in the documentation about $SUBJECT > very confusing: "max_standby_archive_delay must be kept large in this case, > because delayed WAL files might already contain entries that conflict with > the desired standby queries.". After a chat with Andres I've tried to make > it clearer what said statement tries to convey. > > Did I succeed? Don't we need to increase also max_standby_streaming_delay in the case that you mentioned in the patch? When the standby successfully reconnects to the master, lots of WAL files would be streamed and they might already have WAL entries that conflict with standby queries. No? Regards, -- Fujii Masao
В списке pgsql-docs по дате отправления: