Re: Deriving Recovery Snapshots - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Deriving Recovery Snapshots
Date
Msg-id 1224687218.27145.344.camel@ebony.2ndQuadrant
Whole thread Raw
In response to Re: Deriving Recovery Snapshots  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On Wed, 2008-10-22 at 17:40 +0300, Heikki Linnakangas wrote:
> Simon Riggs wrote:
> > If that makes snapshot overflow,
> > we have a big problem: we would be forced to say "sorry snapshot cannot
> > be issued at this time, please wait". Ugh!
> 
> BTW, we'll need to do that anyway, if we guess the max_connections 
> setting in the master incorrectly. We should avoid having to do that 
> under other circumstances, of course.

I'm sure it's easier to handle that in easier ways. I imagined we would
just issue a message saying "must increase max_connections" and then
shutdown. It's easy enough to document that if you change the master you
must also change the slave - it's not a very common change after all.

-- Simon Riggs           www.2ndQuadrant.comPostgreSQL Training, Services and Support



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Deriving Recovery Snapshots
Next
From: Simon Riggs
Date:
Subject: Re: SE-PostgreSQL wiki updates, but ...