| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Exposing an installation's default value of unix_socket_directory |
| Date: | 2010-11-11 06:38:20 |
| Message-ID: | 1289457500.31709.2.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On tor, 2010-10-21 at 16:59 -0400, Tom Lane wrote:
> Actually, the only reason this is even up for discussion is that
> there's
> no configure option to set DEFAULT_PGSOCKET_DIR. If there were, and
> debian were using it, then pg_config --configure would tell what I
> wish
> to know. I thought for a bit about proposing we add such an option,
> but given the current state of play it might be more misleading than
> helpful: as long as distros are accustomed to changing this setting
> via
> a patch, you couldn't trust pg_config --configure to tell you what a
> given installation actually has compiled into it.
Presumably, if a configure option were added, they couldn't change it
via patch anymore. Of course, there will be a transition period, but
there will have to be one of some kind anyway.
Btw., a configure option for this was rejected years ago to discourage
people from actually changing the default.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2010-11-11 11:22:55 | Re: B-tree parent pointer and checkpoints |
| Previous Message | Marko Tiikkaja | 2010-11-11 02:15:34 | wCTE behaviour |