Re: DeArchiver process

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: DeArchiver process
Date: 2011-11-04 13:24:48
Message-ID: CA+Tgmobr6ovLuPB06vTT1rKdSpNSj7QynCC_Gb=SVYMqyYxk9A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Nov 4, 2011 at 5:15 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On Fri, Nov 4, 2011 at 2:36 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
>> If we introduce "walrestore" process, pg_standby seems no longer useful.
>> We should get rid of it?
>
> Removing things too quickly can cause problems. There's no harm done
> by keeping it a while longer.
>
> I agree it should go, just want to be absolutely clear that its no
> longer needed for any use case.

I agree that it would be premature to remove pg_standby at this point.
But how about changing the default value of standby_mode from "off"
to "on" in 9.2? I think most new installations are probably using
that, rather than pg_standby, and changing the default would give
people a gentle push in what now seems to be the preferred direction.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-11-04 13:27:47 Re: Storing original rows before update or delete
Previous Message Magnus Hagander 2011-11-04 13:01:34 Show sequences owned by