Re: max_standby_delay considered harmful - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: max_standby_delay considered harmful
Date
Msg-id 98262e6ddc08b92e913ed7bb559f60dc@biglumber.com
Whole thread Raw
In response to Re: max_standby_delay considered harmful  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


> Based on that, I don't know that there's really much user-seen behaviour
> between the two, except in 'oddball' situations, where there's a time
> skew between the servers, or a large lag, etc, in which case I think

Certainly that one particular case can be solved by making the 
servers be in time sync a prereq for HS working (in the traditional way).
And by "prereq" I mean a "user beware" documentation warning.

- -- 
Greg Sabino Mullane greg@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201005031539
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAkvfJr0ACgkQvJuQZxSWSsgSRwCgwAZpKJDqHX28y90rCx/CNXDt
JGgAoO9JeoBacvTJ09UJ+o1Nek3KtcYR
=gvch
-----END PGP SIGNATURE-----




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: max_standby_delay considered harmful
Next
From: Dimitri Fontaine
Date:
Subject: Re: pg_migrator to /contrib in a later 9.0 beta