Re: recovery_connections cannot start
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Dimitri Fontaine <dfontaine@hi-media.com>
Cc: Simon Riggs <simon@2ndquadrant.com>, Tom Lane <tgl@sss.pgh.pa.us>, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, Kevin Grittner <Kevin.Grittner@wicourts.gov>, Fujii Masao <masao.fujii@gmail.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2010-04-27T11:11:21Z
Lists: pgsql-hackers
On Tue, Apr 27, 2010 at 4:07 AM, Dimitri Fontaine <dfontaine@hi-media.com> wrote: > Robert Haas <robertmhaas@gmail.com> writes: >>> On Mon, 2010-04-26 at 10:41 +0200, Dimitri Fontaine wrote: >>>> 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. >> >> 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. > > I don't see my proposal as anything like a kludge at all. Internal > commands are hugely practical and here would allow for PostgreSQL to > provide basic portable archive and restore commands for simple cases, > providing the necessary guarantees and error management. Treating the string "true" as a special case seems like a kludge to me. Maybe a robust set of internal commands wouldn't be a kludge, but that's not what's being proposed here. I guess it's just a matter of opinion. ...Robert