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

pgsql: Replace max_standby_delay with two parameters,

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Replace max_standby_delay with two parameters,
Date: 2010-07-03 20:43:58
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-committers
Log Message:
Replace max_standby_delay with two parameters, max_standby_archive_delay and
max_standby_streaming_delay, and revise the implementation to avoid assuming
that timestamps found in WAL records can meaningfully be compared to clock
time on the standby server.  Instead, the delay limits are compared to the
elapsed time since we last obtained a new WAL segment from archive or since
we were last "caught up" to WAL data arriving via streaming replication.
This avoids problems with clock skew between primary and standby, as well
as other corner cases that the original coding would misbehave in, such
as the primary server having significant idle time between transactions.
Per my complaint some time ago and considerable ensuing discussion.

Do some desultory editing on the hot standby documentation, too.

Modified Files:
        config.sgml (r1.288 -> r1.289)
        high-availability.sgml (r1.76 -> r1.77)
        xlog.c (r1.427 -> r1.428)
        walreceiver.c (r1.14 -> r1.15)
        walreceiverfuncs.c (r1.5 -> r1.6)
        standby.c (r1.25 -> r1.26)
        proc.c (r1.219 -> r1.220)
        guc.c (r1.557 -> r1.558)
        postgresql.conf.sample (r1.288 -> r1.289)
        xlog.h (r1.113 -> r1.114)
        walreceiver.h (r1.9 -> r1.10)
        standby.h (r1.10 -> r1.11)

pgsql-committers by date

Next:From: Tom LaneDate: 2010-07-03 21:23:58
Subject: pgsql: Make vacuum_defer_cleanup_age be PGC_SIGHUP level, since it's not
Previous:From: Bruce MomjianDate: 2010-07-03 17:21:49
Subject: pgsql: Document more clearly on XML namespaces inside xpath function

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