From: Heikki Linnakangas <hlinnakangas@vmware.com>
To: Joshua D. Drake <jd@commandprompt.com>
To: Peter Eisentraut <peter_e@gmx.net>
To: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: remove pg_standby?
Date: Mon, 10 Nov 2014 20:48:30 +0200
Message-ID: <5461087E.6090003@vmware.com> (raw)
In-Reply-To: <5460FAFF.2000805@commandprompt.com>
References: <545946E9.8060504@gmx.net>
<5460FAFF.2000805@commandprompt.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 11/10/2014 07:50 PM, Joshua D. Drake wrote:
>
> On 11/04/2014 01:36 PM, Peter Eisentraut wrote:
>>
>> While we're talking about removing old things, is there any use left for
>> pg_standby?
>
> -1.
>
> A lot of people, a lot of customers use log shipping for various
> creative and business requirement setups.
Yes, but do they use pg_standby to implement it? If they do, why?
pg_standby is more configurable than the built-in standby_mode=on. You
can set the sleep time, for example, while standby_mode=on uses a
hard-coded delay of 5 s. And pg_standby has a configurable maximum wait
time. And as Fujii pointed out, the built-in system will print an
annoying message to the log every time it attempts to restore a file.
Nevertheless, 99% of users would probably be happy with the built-in thing.
- Heikki
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: hlinnakangas@vmware.com, jd@commandprompt.com, peter_e@gmx.net
Subject: Re: remove pg_standby?
In-Reply-To: <5461087E.6090003@vmware.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox