Re: [COMMITTERS] pgsql: Refactor flex and bison make rules - Mailing list pgsql-hackers

From Jeremy Drake
Subject Re: [COMMITTERS] pgsql: Refactor flex and bison make rules
Date
Msg-id alpine.BSO.2.00.1211282035540.8610@resin.csoft.net
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Refactor flex and bison make rules  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, 28 Nov 2012, Tom Lane wrote:

> Jeremy Drake <pgbuildfarm@jdrake.com> writes:
> > While we're talking about odd issues that only seem to happen on Okapi,
> > does anyone know of anything I can do to diagnose the pg_upgrade failure
> > on the 9.2 branch?  There are no rogue (non-buildfarm-related)
> > postmaster/postgres processes running on the machine.
>
> [ digs around ... ]  It looks like the failure is coming from here:
>
>     if (strlen(path) >= sizeof(unp->sun_path))
>         return EAI_FAIL;
>
> What's the size of the sun_path member of struct sockaddr_un on your
> machine?  I count 115 characters in your socket path ... maybe you
> just need a less deeply nested test directory.
>
> (If that is the problem, seems like we need to return something
> more helpful than EAI_FAIL here.)

/usr/include/sys/un.h:    char sun_path[108];        /* Path name.  */

That seems to be it.  This may be just the excuse I needed to set up
dedicated users for my buildfarm animals.




pgsql-hackers by date:

Previous
From: Jeremy Drake
Date:
Subject: Re: [COMMITTERS] pgsql: Refactor flex and bison make rules
Next
From: Jan Wieck
Date:
Subject: Re: autovacuum truncate exclusive lock round two