Re: Bug with pg_ctl -w/wait and config-only directories - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Bug with pg_ctl -w/wait and config-only directories
Date
Msg-id 5440.1317774763@sss.pgh.pa.us
Whole thread Raw
In response to Re: Bug with pg_ctl -w/wait and config-only directories  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Bug with pg_ctl -w/wait and config-only directories
Re: Bug with pg_ctl -w/wait and config-only directories
List pgsql-hackers
Bruce Momjian <bruce@momjian.us> writes:
> Tom Lane wrote:
>> As of fairly recently, the Fedora package also uses pg_ctl for both
>> starting and stopping.  We've fixed all the reasons that formerly
>> existed to avoid use of pg_ctl, and it's a real PITA to try to
>> implement the waiting logic at shell level.

> OK, that's a good use-case to warrant barrelling ahead with improving
> pg_ctl for config-only installs.

Did I say that?  The Fedora packages don't support config-only
arrangements (if you tried, SELinux would likely deny access to whatever
directory you chose ...)

> What releases do we want to apply that
> patch to allow postgres to dump config values and have pg_ctl use them? 
> This patch is required for old/new installs for pg_upgrade to work.

I still think this is a matter for HEAD only.  We haven't supported
these cases in back branches and so there is little argument for
back-patching.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Bug with pg_ctl -w/wait and config-only directories
Next
From: Bruce Momjian
Date:
Subject: Re: Inlining comparators as a performance optimisation