| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Cédric Villemain <cedric(dot)villemain(dot)debian(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Exposing an installation's default value of unix_socket_directory |
| Date: | 2010-10-21 20:10:43 |
| Message-ID: | 5271.1287691843@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 Cdric Villemain's message of jue oct 21 16:01:30 -0300 2010:
>> 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.
> Yeah -- how is pg_config to know? All it can tell you is what was the
> compiled-in default.
That's what I wanted, actually. If you've set a non-default value in
postgresql.conf, SHOW will tell you about that, but it fails to expose
the default value.
> Maybe you should go the SHOW route. The user could connect via TCP and
> find out the socket directory that way.
Yeah, the SHOW case is not useless by any means.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-10-21 20:19:42 | Re: Exposing an installation's default value of unix_socket_directory |
| Previous Message | Greg Stark | 2010-10-21 20:03:07 | Re: pg_rawdump |