Re: recovery_connections cannot start (was Re: master in standby mode croaks) - Mailing list pgsql-hackers

From Robert Haas
Subject Re: recovery_connections cannot start (was Re: master in standby mode croaks)
Date
Msg-id m2q603c8f071004231429jc7a41dcah4aeb727172db328f@mail.gmail.com
Whole thread Raw
In response to Re: recovery_connections cannot start (was Re: master in standby mode croaks)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: recovery_connections cannot start (was Re: master in standby mode croaks)  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
On Fri, Apr 23, 2010 at 4:50 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Simon Riggs <simon@2ndQuadrant.com> writes:
>> How about something like
>
>> wal_additional_info = none | archive | connect
>
> "connect" seems like a completely inappropriate word here.  It is
> not obviously related to HS slaves and it could be taken to refer
> to ordinary database connections (sessions).
>
> Personally I agree with your objection to "crash" but not with the
> objection to "standby".  Maybe this would be appropriate:
>
>        wal_mode = minimal | archive | hot_standby

I was thinking maybe "log_shipping" instead of "archive", since we're
conflating the technology (log shipping) with the technology used to
implement it (archiving or streaming).

Possible "crash_recovery" rather than just "crash" where you have "mimimal".

I don't love "hot_standby" either but it might be the least of evils.

...Robert


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Make CheckRequiredParameterValues() depend upon correct
Next
From: Simon Riggs
Date:
Subject: Re: recovery_connections cannot start (was Re: master in standby mode croaks)