On Mon, Jul 2, 2012 at 12:44 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> On Sun, Jul 1, 2012 at 1:02 PM, Boszormenyi Zoltan <zb(at)cybertec(dot)at> wrote:
>> attached is a patch that does $SUBJECT.
>> It's a usability enhancement, to take a backup, write
>> a minimalistic recovery.conf and start the streaming
>> standby in one go.
> I like the writing of recovery.conf.
> In fact, I had it in my code at
> one very early point and took it out in order to get a clean patch
> ready :)
> But I think that part is lacking in functionality: AFAICT it's
> hardcoded to only handle host, port, user and password. What about
> other connection parameters, likely passed to pg_basebackup through
> the environment in that case? isn't that quite likely to break the
> server later?
What about something like PQconninfo which returns the connection
string value established at connection?
> Maybe the proper way around that is to provide the ability for
> pg_basebackup to take a full connection string, just like we allow
> psql to do?
> I'm not sure we should go the way of providing the "start slave".
> Given thta how you want to start the slave differs so much on
> platforms. The most glaring example is on windows you really need to
> *start the service* rather than use pg_ctl. Sure, you can document
> your way around that, but I'm not sure the functionality added is
> really worth it.
In response to
pgsql-hackers by date
|Next:||From: Stefan Kaltenbrunner||Date: 2012-07-01 17:04:18|
|Subject: compiler warnings on the buildfarm|
|Previous:||From: Fujii Masao||Date: 2012-07-01 16:01:43|
|Subject: Re: [PATCH] Make pg_basebackup configure and start standby|