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

Re: Hot Standby and handling max_standby_delay

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Hot Standby and handling max_standby_delay
Date: 2010-01-16 17:51:37
Message-ID: 1263664298.26654.50515.camel@ebony (view raw or flat)
Thread:
Lists: pgsql-hackers
On Fri, 2010-01-15 at 20:50 +0200, Heikki Linnakangas wrote:

> That would change the meaning of max_standby_delay. Currently, it's the
> delay between *generating* and applying a WAL record, your proposal
> would change it to mean delay between receiving and applying it. That
> seems a lot less useful to me.

It would be good if there was a keepalive WAL record with a timestamp on
it generated every N seconds while in streaming mode.

-- 
 Simon Riggs           www.2ndQuadrant.com


In response to

pgsql-hackers by date

Next:From: Simon RiggsDate: 2010-01-16 18:20:37
Subject: Re: Hot Standby and handling max_standby_delay
Previous:From: Stefan KaltenbrunnerDate: 2010-01-16 17:22:57
Subject: Re: Streaming replication status

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