Re: recovery_connections cannot start - Mailing list pgsql-hackers

From Robert Haas
Subject Re: recovery_connections cannot start
Date
Msg-id u2h603c8f071004260329t13cf584bqf1d687a68df2a8f9@mail.gmail.com
Whole thread Raw
In response to Re: recovery_connections cannot start  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: recovery_connections cannot start  (Dimitri Fontaine <dfontaine@hi-media.com>)
List pgsql-hackers
On Mon, Apr 26, 2010 at 6:08 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
> On Mon, 2010-04-26 at 10:41 +0200, Dimitri Fontaine wrote:
>> Tom Lane <tgl@sss.pgh.pa.us> writes:
>> >   The only workable
>> > alternative I can see to keeping archive_mode is to tell people to
>> > set archive_command to something like /usr/bin/true ... which is not
>> > simpler, especially not on Windows.
>>
>> Would it be possible to have "internal" commands there, as for example
>> cd is in my shell, or test, or time, or some more ?
>>
>> That would allow for providing a portable /usr/bin/true command as far
>> as archiving is concerned (say, pg_archive_bypass), and will allow for
>> providing a default archiving command in the future, like "pg_archive_cp
>> /location" or something.
>
> I think making a special case here is OK.
>
> If command string == 'true' then we don't bother to call system(3) at
> all, we just assume it worked fine.
>
> That way we have a simple route on all platforms.

Separating wal_mode and archive_mode, as we recently discussed, might
eliminate the need for this kludge, if archive_mode can then be made
changeable without a restart.

...Robert


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: recovery_connections cannot start (was Re: master in standby mode croaks)
Next
From: Robert Haas
Date:
Subject: Re: don't allow walsender to consume superuser_reserved_connection slots, or during shutdown