Re: recovery_connections cannot start - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: recovery_connections cannot start
Date
Msg-id 1272276529.4161.3208.camel@ebony
Whole thread Raw
In response to Re: recovery_connections cannot start  (Dimitri Fontaine <dfontaine@hi-media.com>)
Responses Re: recovery_connections cannot start  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
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.

-- Simon Riggs           www.2ndQuadrant.com



pgsql-hackers by date:

Previous
From: Takahiro Itagaki
Date:
Subject: Re: CIText and pattern_ops
Next
From: Robert Haas
Date:
Subject: Re: including PID or backend ID in relpath of temp rels