Added to TODO:
Allow simpler reporting of the unix domain socket directory and allow
easier configuration of its default location
* http://archives.postgresql.org/pgsql-hackers/2010-10/msg01555.php
---
Tom Lane wrote:
> Peter Eisentraut writes:
> > 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 -
Peter Eisentraut writes:
> 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
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 fo
"A.M." writes:
> On Oct 21, 2010, at 4:19 PM, Robert Haas wrote:
>> I think adding this to pg_config is sensible. Sure, the user could
>> have moved the socket directory. But it's a place to start looking.
>> So why not?
> Because pg_config is supposed to return the current state of a cluster?
On Oct 21, 2010, at 4:19 PM, Robert Haas wrote:
> 2010/10/21 Tom Lane :
>> Alvaro Herrera writes:
>>> Excerpts from Cédric 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 th
2010/10/21 Tom Lane :
> Alvaro Herrera writes:
>> Excerpts from Cédric 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...
Alvaro Herrera writes:
> Excerpts from Cédric 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 a
Tom Lane writes:
> 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?
Following some links one can find out
http://packages.de
Excerpts from Cédric 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 i
2010/10/21 Tom Lane :
> 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) th
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 argument
12 matches
Mail list logo
