From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: Yet another issue with pg_upgrade vs unix_socket_directories |
Date: | 2012-09-04 17:44:59 |
Message-ID: | 50463E1B.9030903@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 9/3/12 5:00 PM, Tom Lane wrote:
> I went back for another try at building the Fedora packages with 9.2
> branch tip ... and it still failed at pg_upgrade's "make check".
> The reason for this is that test.sh starts a couple of random
> postmasters, and those postmasters expect to put their sockets in
> the configured default location (which is now /var/run/postgresql
> on Fedora), and that's not there in a minimal build environment.
And if it's there, it might not be writable.
> I hacked it up with the attached quick-and-dirty patch, but I wonder
> if anyone's got a better idea.
Yeah, I have resorted to putting something like
export PGHOST=/tmp
in all my test scripts, because the above-mentioned issues have affected
Debian for a long time. Welcome to the party. ;-)
It might actually be useful if the postmaster accepted PGHOST as the
default value for the -k option, just like it accepts PGPORT. Then this
type setup will become much easier because clients and servers will use
the same defaults.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2012-09-04 18:04:04 | Re: Yet another issue with pg_upgrade vs unix_socket_directories |
Previous Message | Daniel Farina | 2012-09-04 16:46:58 | Re: txid failed epoch increment, again, aka 6291 |