Robert Haas <robertmh...@gmail.com> writes: > I haven't been able to wrap my head around why the delay should be > LESS in the archive case than in the streaming case. Can you attempt > to hit me with the clue-by-four?
In the archive case, you're presumably trying to catch up, and so it makes sense to kill queries faster so you can catch up. The existing code essentially forces instant kill when reading from archive, for any reasonable value of max_standby_delay (because the archived timestamps will probably be older than that). That's overenthusiastic in my view, but you can get that behavior if you want it with this patch by setting max_standby_archive_delay to zero. If you don't want it, you can use something larger. If you don't think that max_standby_archive_delay should be less than max_standby_streaming_delay, you can set them the same, too. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers