Prev: [HACKERS] Generating Lots of PKs with nextval(): A Feature Proposal
Next: recovery consistent != hot standby
From: Bruce Momjian on 14 May 2010 17:12
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(a)momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: "Kevin Grittner" on 14 May 2010 17:19
Bruce Momjian <bruce(a)momjian.us> wrote:

> 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.

Why? I read that as saying that the master is writing sufficient
data into the WAL for it to be usable for hot standby purposes, and
that that the slave machine is going to be used as a hot standby.
You'd better do the former if you're going to do the latter, but
there were good reasons not to try to infer one setting from the
other.

-Kevin

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

 | 
Pages: 1
Prev: [HACKERS] Generating Lots of PKs with nextval(): A Feature Proposal
Next: recovery consistent != hot standby