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

Re: Hot Standby and handling 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: Simon Riggs <simon(at)2ndQuadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Hot Standby and handling max_standby_delay
Date: 2010-01-18 17:30:19
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Tom Lane wrote:
> Speaking of which, just where is the defense that makes sure that
> walsender and walreceiver are compatible?  We should be checking not
> only version, but all of the configuration variables that are embedded
> in pg_control.

That happens at startup when pg_control is read, before streaming
starts. Remember that you need to start with a base backup.

We also check that the system_identifier in the standby matches that in
the primary, when the connection is established. That protects you from
starting streaming from wrong base backup.

  Heikki Linnakangas

In response to

pgsql-hackers by date

Next:From: Matteo BeccatiDate: 2010-01-18 17:31:08
Subject: Re: mailing list archiver chewing patches
Previous:From: Greg StarkDate: 2010-01-18 16:35:59
Subject: Re: Faster CREATE DATABASE by delaying fsync (was 8.4.1 ubuntu karmic slow createdb)

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