pgsql: Revert exporting of internal GUC variable "data_directory".

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Revert exporting of internal GUC variable "data_directory".
Date: 2015-05-29 15:57:38
Message-ID: E1YyMfC-0001Ov-VA@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Revert exporting of internal GUC variable "data_directory".

This undoes a poorly-thought-out choice in commit 970a18687f9b3058, namely
to export guc.c's internal variable data_directory. The authoritative
variable so far as C code is concerned is DataDir; there is no reason for
anything except specific bits of GUC code to look at the GUC variable.

After yesterday's commits fixing the fsync-on-restart patch, the only
remaining misuse of data_directory was in AlterSystemSetConfigFile(),
which would be much better off just using a relative path anyhow: it's
less code and it doesn't break if the DBA moves the data directory of a
running system, which is a case we've taken some pains over in the past.

This is mostly cosmetic, so no need for a back-patch (and I'd be hesitant
to remove a global variable in stable branches anyway).

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/da33a3894e0fc440ac53cdc0f2e360e703b13b8c

Modified Files
--------------
src/backend/utils/misc/guc.c | 10 +++++-----
src/include/utils/guc.h | 1 -
2 files changed, 5 insertions(+), 6 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2015-05-29 17:05:30 pgsql: Adjust initdb to also not consider fsync'ing failures fatal.
Previous Message Tom Lane 2015-05-28 21:33:25 pgsql: Fix fsync-at-startup code to not treat errors as fatal.