On 30/08/10 15:14, Fujii Masao wrote:
> I think that the advantage of registering standbys is that we can
> specify which WAL files the master has to keep for the upcoming
> standby. IMO, it's usually called together with pg_start_backup
> as follows:
> SELECT register_standby('foo', pg_start_backup())
> This requests the master keep to all the WAL files following the
> backup starting location which pg_start_backup returns.
Hmm, that's clever. I was thinking that you'd initialize the standby
from an existing backup, and in that context the standby would not need
to connect to the master except via the replication connection. To take
a base backup, you'll need not only that but also access to the
filesystem in the master, ie. shell access.
There's been some talk of being able to stream a base backup over the
replication connection too, which would be extremely handy. And that
makes my point even stronger that registering a standby should be
possible via the replication connection.
Of course, you could well expose the functionality as both a built-in
function and a command in replication mode, so this detail isn't really
that important right now.
In response to
pgsql-hackers by date
|Next:||From: Michael Meskes||Date: 2010-09-01 14:41:07|
|Subject: Re: ECPG dynamic cursor fix for UPDATE/DELETE ... WHERE CURRENT OF
|Previous:||From: PostgreSQL - Hans-Jürgen Schönig||Date: 2010-09-01 14:28:06|
|Subject: Re: Path question |