Re: max_standby_delay considered harmful - Mailing list pgsql-hackers

From Greg Smith
Subject Re: max_standby_delay considered harmful
Date
Msg-id 4BE2B94C.5080603@2ndquadrant.com
Whole thread Raw
In response to Re: max_standby_delay considered harmful  (Yeb Havinga <yebhavinga@gmail.com>)
List pgsql-hackers
Yeb Havinga wrote:
> Rob Wultsch wrote:
>> I can not imagine setting this value to anything other than a bool and
>> most of the time that bool would be -1.
> That's funny because when I was reading this thread, I was thinking 
> the exact opposite: having max_standby_delay always set to 0 so I know 
> the standby server is as up-to-date as possible.

If you ask one person about this, you'll discover they only consider one 
behavior here sane, and any other setting is crazy.  Ask five people, 
and you'll likely find someone who believes the complete opposite.  Ask 
ten and carefully work out the trade-offs they're willing to make given 
the fundamental limitations of replication, and you'll arrive at the 
range of behaviors available right now, plus some more that haven't been 
built yet.  There are a lot of different types of database applications 
out there, each with their own reliability and speed requirements to 
balance.

-- 
Greg Smith  2ndQuadrant US  Baltimore, MD
PostgreSQL Training, Services and Support
greg@2ndQuadrant.com   www.2ndQuadrant.us



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: LD_LIBRARY_PATH versus rpath
Next
From: Bruce Momjian
Date:
Subject: Re: pg_migrator to /contrib in a later 9.0 beta