| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> | 
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> | 
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> | 
| Subject: | Re: Hot Standby remaining issues | 
| Date: | 2009-12-02 16:45:46 | 
| Message-ID: | 1259772346.13774.23413.camel@ebony | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
On Wed, 2009-12-02 at 16:41 +0000, Simon Riggs wrote:
> On Tue, 2009-12-01 at 20:26 +0200, Heikki Linnakangas wrote:
> > Simon Riggs wrote:
> > > commit 02c3eadb766201db084b668daa271db4a900adc9
> > > Author: Simon Riggs <sriggs(at)ebony(dot)(none)>
> > > Date:   Sat Nov 28 06:23:33 2009 +0000
> > > 
> > >     Added wal_standby_info GUC to turn RM_STANDBY_ID messages on/off.
> > >     Various comments added also.
> > > 
> > 
> > This patch makes it unsafe to start hot standby mode from a shutdown
> > checkpoint, because we don't know if wal_standby_info was enabled in the
> > master.
Hmm, what happens if someone enables wal_standby_info in postgresql.conf
while the server is shutdown. It would still be a valid starting point
in that case. I'll just make a note, I think.
-- 
 Simon Riggs           www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-12-02 16:47:44 | Re: Cost of sort/order by not estimated by the query planner | 
| Previous Message | Simon Riggs | 2009-12-02 16:41:53 | Re: Hot Standby remaining issues |