Skip site navigation (1) Skip section navigation (2)

Re: Keepalive for max_standby_delay

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Keepalive for max_standby_delay
Date: 2010-07-03 11:59:10
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On 02/07/10 23:36, Tom Lane wrote:
> Robert Haas<robertmhaas(at)gmail(dot)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.

It would seem logical to use the same logic for archive recovery as we 
do for streaming replication, and only set XLogReceiptTime when you have 
to wait for a WAL segment to arrive into the archive, ie. when 
restore_command fails.

   Heikki Linnakangas

In response to


pgsql-hackers by date

Next:From: Robert HaasDate: 2010-07-03 14:13:09
Subject: Re: reassign owned to change the ownership for op class and family
Previous:From: Robert HaasDate: 2010-07-03 11:02:40
Subject: Re: Keeping separate WAL segments for each database

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group