Re: Dividing progress/debug information in pg_standby, and stat before copy - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Dividing progress/debug information in pg_standby, and stat before copy
Date
Msg-id 4B5F3914.8070503@enterprisedb.com
Whole thread Raw
In response to Re: Dividing progress/debug information in pg_standby, and stat before copy  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Dividing progress/debug information in pg_standby, and stat before copy
List pgsql-hackers
Josh Berkus wrote:
>> *That* makes pg_standby obsolete, not streaming replication per se.
>> Setting standby_mode=on, with a valid restore_command using e.g 'cp' and
>> no connection info for walreceiver is more or less the same as using
>> pg_standby.
> 
> What about deletion of no-longer-needed WALfile copies?

Yeah, good point. You can still use a shell script as restore_command,
pass the %r option to it, and do the deletion there.

I didn't intend to replace pg_standby when I started this, it just kind
of happened. Maybe we should provide a sample script similar to
pg_standby, to be used instead of plain 'cp', that does the cleanup too.

--  Heikki Linnakangas EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Joe Conway
Date:
Subject: Re: Patch: libpq new connect function (PQconnectParams)
Next
From: Josh Berkus
Date:
Subject: Re: Dividing progress/debug information in pg_standby, and stat before copy