Skip site navigation (1) Skip section navigation (2)

Re: Overlength socket paths (was Re: [COMMITTERS] pgsql: Refactor flex and bison make rules)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Jeremy Drake <pgbuildfarm(at)jdrake(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Overlength socket paths (was Re: [COMMITTERS] pgsql: Refactor flex and bison make rules)
Date: 2012-11-30 00:32:31
Message-ID: 23298.1354235551@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 11/29/2012 07:16 PM, Tom Lane wrote:
>> Um ... that's *another* place that needs to change then, because the
>> test script fires up postmasters on its own, outside of pg_upgrade.

> True, but it doesn't do anything about setting the socket dir, so those 
> just get the compiled-in defaults. What exactly do you want to change 
> about the test script?

Well, I was thinking about also solving the problem that the compiled-in
default might be no good in a build environment.

			regards, tom lane


In response to

pgsql-hackers by date

Next:From: Michael PaquierDate: 2012-11-30 00:56:34
Subject: Re: Bugs in CREATE/DROP INDEX CONCURRENTLY
Previous:From: Andrew DunstanDate: 2012-11-30 00:24:32
Subject: Re: Overlength socket paths (was Re: [COMMITTERS] pgsql: Refactor flex and bison make rules)

pgsql-committers by date

Next:From: Tom LaneDate: 2012-11-30 00:58:17
Subject: pgsql: Produce a more useful error message for over-length Unixsocket
Previous:From: Andrew DunstanDate: 2012-11-30 00:24:32
Subject: Re: Overlength socket paths (was Re: [COMMITTERS] pgsql: Refactor flex and bison make rules)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group