From: | Cédric Villemain <cedric(dot)villemain(dot)debian(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Exposing an installation's default value of unix_socket_directory |
Date: | 2010-10-21 19:01:30 |
Message-ID: | AANLkTinSA-ME9fteP1b5UYZ8UhZfFVHWweh40ojL2UFs@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2010/10/21 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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(at)postgresql(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-10-21 19:06:33 | Re: Per-column collation, work in progress |
Previous Message | Alvaro Herrera | 2010-10-21 18:48:57 | Re: Bug in plpython's Python Generators |