Re: Hot standby v5 patch - restarted replica changes to warm standby mode - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Hot standby v5 patch - restarted replica changes to warm standby mode
Date
Msg-id 1225783887.3971.1062.camel@ebony.2ndQuadrant
Whole thread Raw
In response to Hot standby v5 patch - restarted replica changes to warm standby mode  (Mark Kirkwood <markir@paradise.net.nz>)
Responses Re: Re: Hot standby v5 patch - restarted replica changes to warm standby mode
List pgsql-hackers
On Tue, 2008-11-04 at 18:33 +1300, Mark Kirkwood wrote:
> While doing some tests yesterday I ran into the situation where the 
> standby database would appear to go back into 'warm' mode after it was 
> restarted. The set of steps to reproduce the behaviour is:
> 
> 1/ Setup master and replica with replica using pg_standby
> 2/ Initialize pgbench schema with size 100 in database 'postgres'
> 3/ Connect to replica, then disconnect (this step is not necessary I 
> *think* - just for checking that connection works at this point!)
> 4/ Shutdown and restart the replica - there is no "database has now 
> reached consistent state" message in the log, and you cannot connect

How did you shutdown the database? Fast? Immediate mode acts just as it
does on an unpatched server.

Can you give more details of exactly what you did? Thanks. Not saying
there isn't a problem, just don't understand what happened.

Not being able to connect after a restart is a design feature, to
protect you from running potentially invalid queries.

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



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Hot standby v5 patch - Databases created post backup remain inaccessible + replica SIGSEGV when coming out of standby
Next
From: "Hannes Eder"
Date:
Subject: Re: Get Date value from Datum