Re: Parameter oddness; was HS/SR Assert server crash

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Parameter oddness; was HS/SR Assert server crash
Date: 2010-05-14 21:12:09
Message-ID: 201005142112.o4ELC9t18223@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

bruce wrote:
> > and my slave recovery.conf was:
> >
> > restore_command = 'cp /u/pg/archive/%f %p' # e.g. 'cp /mnt/server/archivedir/%f %p'
> > standby_mode = 'on'
> > primary_conninfo = 'host=localhost port=5432' # e.g. 'host=localhost port=5432'
> >
> > Let me know what additional information I can supply.
>
> I saw Simon's commit fixing this bug. Another good reason we didn't
> bundle 9.0 beta2 yesterday.

I can now confirm that Simon's patch fixes the bug. (Unfortunately I
had a web cast yesterday about this feature and the bug prevented me
from completing the demonstration.)

FYI, my presentation shows all the steps necessary to setup HS/SR:

http://momjian.us/main/presentations/technical.html#hot_streaming

One odd thing is we have two paramters that mention hot_standby --- on
the master we have to do in postgresql.conf:

wal_level = hot_standby

and on the slave we do in postgresql.conf:

hot_standby = on

That is a little confusing.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2010-05-14 21:19:03 Re: Parameter oddness; was HS/SR Assert server crash
Previous Message Kevin Grittner 2010-05-14 21:09:21 Re: List traffic