Robert Haas wrote:
> On Wed, Jun 1, 2011 at 7:07 PM, Tom Lane wrote:
> > Alvaro Herrera writes:
> >> Excerpts from Robert Haas's message of mi? jun 01 18:22:56 -0400 2011:
> >>> ISTM that it would be useful to run postgres in a mode where it
> >>> doesn't actually try to start up the database, bu
On Wed, Jun 1, 2011 at 7:07 PM, Tom Lane wrote:
> Alvaro Herrera writes:
>> Excerpts from Robert Haas's message of mié jun 01 18:22:56 -0400 2011:
>>> ISTM that it would be useful to run postgres in a mode where it
>>> doesn't actually try to start up the database, but parses
>>> postgresql.conf
Alvaro Herrera writes:
> Excerpts from Robert Haas's message of mié jun 01 18:22:56 -0400 2011:
>> ISTM that it would be useful to run postgres in a mode where it
>> doesn't actually try to start up the database, but parses
>> postgresql.conf and then exits, perhaps printing out the value of a
>>
Excerpts from Robert Haas's message of mié jun 01 18:22:56 -0400 2011:
> ISTM that it would be useful to run postgres in a mode where it
> doesn't actually try to start up the database, but parses
> postgresql.conf and then exits, perhaps printing out the value of a
> certain GUC as it does so. I
> No, it isn't. You're making way too many assumptions about where things
> really were and what arguments were given to pg_ctl start. We went
> around on this before, which is why it's not "fixed" already.
What should I search on? I can't find the relevant discussion.
--
Josh Berkus
Postgre
On Wed, Jun 1, 2011 at 5:10 PM, Tom Lane wrote:
> Josh Berkus writes:
>> pg_ctl -D means different things depending on whether you are calling
>> "start" or "stop". For "start", pg_ctl wants the directory
>> postgresql.conf is in, and for "stop" it wants the directory
>> postmaster.pid is in. T
On Wed, Jun 1, 2011 at 4:10 PM, Tom Lane wrote:
>
> I can't speak for Debian, but the above statement is 100% false for Red
> Hat. In any case, no RH system has ever expected users to issue pg_ctl
> start/stop directly, and I think the same is true for Debian, so the
> bizarre design wouldn't mat
Josh Berkus writes:
> pg_ctl -D means different things depending on whether you are calling
> "start" or "stop". For "start", pg_ctl wants the directory
> postgresql.conf is in, and for "stop" it wants the directory
> postmaster.pid is in. This means that if your .conf files are not in
> the sam
All,
pg_ctl -D means different things depending on whether you are calling
"start" or "stop". For "start", pg_ctl wants the directory
postgresql.conf is in, and for "stop" it wants the directory
postmaster.pid is in. This means that if your .conf files are not in
the same directory as data_direc
