Re: [HACKERS] Add socket dir to pg_config..?

2011-10-31 Thread Cédric Villemain
2011/10/30 Martijn van Oosterhout klep...@svana.org: On Sat, Oct 29, 2011 at 08:28:57PM +, Mr. Aaron W. Swenson wrote: If /tmp is the only decent place where to put the socket file on Unix when security and other concerns are considered, then sure, making distro life difficult is a good

Re: [HACKERS] Add socket dir to pg_config..?

2011-10-30 Thread Martijn van Oosterhout
On Sat, Oct 29, 2011 at 08:28:57PM +, Mr. Aaron W. Swenson wrote: If /tmp is the only decent place where to put the socket file on Unix when security and other concerns are considered, then sure, making distro life difficult is a good thing to do. But then let's take it to the FHS that

Re: [HACKERS] Add socket dir to pg_config..?

2011-10-29 Thread Greg Stark
On Fri, Oct 28, 2011 at 5:33 PM, Dimitri Fontaine dimi...@2ndquadrant.fr wrote: I'm puzzled, maybe I'm not understanding a key point here though. I think the only thing you're missing here is that, despite appearances some days, Postgres is not run by a single hive mind. Tom thinks there needs

Re: [HACKERS] Add socket dir to pg_config..?

2011-10-29 Thread Mr. Aaron W. Swenson
On Fri, Oct 28, 2011 at 06:33:39PM +0200, Dimitri Fontaine wrote: Andrew Dunstan and...@dunslane.net writes: Er, which distros other than debian/ubuntu? Well, any and all derivatives I guess, to begin with. http://distrowatch.com/dwres.php?resource=independence#debian Based on Debian

Re: [HACKERS] Add socket dir to pg_config..?

2011-10-28 Thread Cédric Villemain
2011/10/28 Tom Lane t...@sss.pgh.pa.us: Stephen Frost sfr...@snowman.net writes:   Was just wondering if we might want to include the default socket   directory that was compiled in as part of the pg_config output..? [ shrug... ]  We don't report the compiled-in port number, which is

Re: [HACKERS] Add socket dir to pg_config..?

2011-10-28 Thread Stephen Frost
* Tom Lane (t...@sss.pgh.pa.us) wrote: [ shrug... ] We don't report the compiled-in port number, which is considerably more critical. And we don't report changes in any of the other stuff in pg_config_manual.h. True. MHO is that changing the socket directory is only marginally supported,

Re: [HACKERS] Add socket dir to pg_config..?

2011-10-28 Thread Andrew Dunstan
On 10/28/2011 08:01 AM, Stephen Frost wrote: MHO is that changing the socket directory is only marginally supported, and we shouldn't encourage it unless we're prepared to fully support it (which we can't really). This concerns me a bit, as most distros change it.. What would you expect

Re: [HACKERS] Add socket dir to pg_config..?

2011-10-28 Thread Dimitri Fontaine
Andrew Dunstan and...@dunslane.net writes: Er, which distros other than debian/ubuntu? Well, any and all derivatives I guess, to begin with. http://distrowatch.com/dwres.php?resource=independence#debian Based on Debian GNU/Linux: 129 Distributions More seriously, I'm not sure how to

[HACKERS] Add socket dir to pg_config..?

2011-10-27 Thread Stephen Frost
All, Was just wondering if we might want to include the default socket directory that was compiled in as part of the pg_config output..? Thanks, Stephen signature.asc Description: Digital signature

Re: [HACKERS] Add socket dir to pg_config..?

2011-10-27 Thread Tom Lane
Stephen Frost sfr...@snowman.net writes: Was just wondering if we might want to include the default socket directory that was compiled in as part of the pg_config output..? [ shrug... ] We don't report the compiled-in port number, which is considerably more critical. And we don't report