Re: Exposing an installation's default value of unix_socket_directory - Mailing list pgsql-hackers

From Cédric Villemain
Subject Re: Exposing an installation's default value of unix_socket_directory
Date
Msg-id AANLkTinSA-ME9fteP1b5UYZ8UhZfFVHWweh40ojL2UFs@mail.gmail.com
Whole thread Raw
In response to Exposing an installation's default value of unix_socket_directory  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Exposing an installation's default value of unix_socket_directory
List pgsql-hackers
2010/10/21 Tom Lane <tgl@sss.pgh.pa.us>:
> I just noticed that there doesn't seem to be any good way of finding
> out what a postmaster's default value of unix_socket_directory is.
> If you try to SHOW it you just get an empty string.  We could probably
> fix things so that SHOW exposes the actual setting, but (1) there might
> be security arguments against that, and (2) if your problem is that you
> would like to find out the value so's you can connect to said
> postmaster, SHOW isn't going to help you.
>
> One possible response would be to add an item to what pg_config knows
> about, eg "pg_config --socketdir".  This doesn't answer every possible
> use-case either, but it would be helpful for some scenarios.
>
> Thoughts?

I agree this is interesting information to get, but wonder how
pg_config can know that and it looks to me that this information as
nothing to do in pg_config....

pg_config is all about installation, socket_dir is a postgresql.conf setting.

I'd prefer a 'pg_ctl status' output.

>
>                        regards, tom lane
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>



--
Cédric Villemain               2ndQuadrant
http://2ndQuadrant.fr/     PostgreSQL : Expertise, Formation et Support


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Bug in plpython's Python Generators
Next
From: Robert Haas
Date:
Subject: Re: Per-column collation, work in progress