Re: remove pg_standby?

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: remove pg_standby?
Date: 2014-11-10 17:19:52
Message-ID: CABUevEz-ZG45mQvnSPOKBz==N9T-RTgS+QGit4EuKtQUM1pi-Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Nov 10, 2014 6:16 PM, "Fujii Masao" <masao(dot)fujii(at)gmail(dot)com> wrote:
>
> On Wed, Nov 5, 2014 at 6:36 AM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> > While we're talking about removing old things, is there any use left for
> > pg_standby?
>
> -1 for removing it. There is still the case where I'd like to use
log-shipping
> rather than replication. For example, it's the case where I need to
> compress WAL files before streaming them via very thin network.
> We can set up log-shipping using standby_mode and without using
> pg_standby, but it keeps emitting the failure of restore_command while
> while there is no WAL activity, and which is bothersome. So I still need
> pg_standby for log-shipping.

I didn't realize that part, but maybe we should fix that instead of keeping
pg_standby around?

(BTW, you can use streaming with compression as well using ssl of course,
but it won't get quite the same levels due to smaller block sizes. And
there are certainly still reasons for file based standbys so we should
definitely not remove that)

/Magnus

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2014-11-10 17:28:30 Re: Proposal: Log inability to lock pages during vacuum
Previous Message Fujii Masao 2014-11-10 17:16:18 Re: remove pg_standby?