Re: Bad UI design: pg_ctl and data_directory

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Bad UI design: pg_ctl and data_directory
Date: 2011-06-01 23:07:07
Message-ID: 27992.1306969627@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)commandprompt(dot)com> 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
>> certain GUC as it does so. In this case, data_directory.

> I had the same thought, and wondered if we could use the feature
> elsewhere.

This was suggested quite some time ago, IIRC, but we never got round to it.

The main problem in the current context is that it only fixes the issue
so long as you ignore the possibility that relevant values were
specified on the command line or via environment variables, rather than
coming directly from the config file. PGDATA is thus a particular
hazard here: all you need is to be running with a different PGDATA
setting in your environment than was used when "pg_ctl start" was
issued, and you're hosed.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2011-06-01 23:08:16 Re: pgpool versus sequences
Previous Message Alvaro Herrera 2011-06-01 22:57:21 Re: Bad UI design: pg_ctl and data_directory