Re: Re: Sure enough, the lock file is gone - Mailing list pgsql-hackers

From teg@redhat.com (Trond Eivind Glomsrød)
Subject Re: Re: Sure enough, the lock file is gone
Date
Msg-id xuyelxnzhwf.fsf@halden.devel.redhat.com
Whole thread Raw
In response to Re: Re: Sure enough, the lock file is gone  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Re: Sure enough, the lock file is gone  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane <tgl@sss.pgh.pa.us> writes:

> It would probably be better if the socket files weren't in /tmp but in
> a postgres-owned directory.  However, at this point we have a huge
> backwards compatibility problem to overcome if we want to move the
> socket files.

Not to sound scheptical, but since when did postgresql care about
backwards compatiblity? Upgrading is already demanding a lot of
knowledge from the user (including needing such information, which
almost no other package do), this is just a minor change (the files
are mostly used by bundled tools - any exceptions?)

> There is an option in 7.1 to support defining a different directory
> for the socket files, but I doubt very many people will use it.

I intend to, for the RPMs we ship.

-- 
Trond Eivind Glomsrød
Red Hat, Inc.


pgsql-hackers by date:

Previous
From: "Oliver Elphick"
Date:
Subject: Re: Re: [GENERAL] MySQL -> Postgres dump converter
Next
From: Tom Lane
Date:
Subject: Re: Re: Sure enough, the lock file is gone