From: | Jeremy Drake <pgbuildfarm(at)jdrake(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
Subject: | Re: [COMMITTERS] pgsql: Refactor flex and bison make rules |
Date: | 2012-11-29 04:49:14 |
Message-ID: | alpine.BSO.2.00.1211282035540.8610@resin.csoft.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Wed, 28 Nov 2012, Tom Lane wrote:
> Jeremy Drake <pgbuildfarm(at)jdrake(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-11-29 15:38:10 | pgsql: Fix assorted bugs in CREATE/DROP INDEX CONCURRENTLY. |
Previous Message | Tom Lane | 2012-11-29 04:03:01 | Re: [COMMITTERS] pgsql: Refactor flex and bison make rules |
From | Date | Subject | |
---|---|---|---|
Next Message | Pavan Deolasee | 2012-11-29 04:50:12 | Re: Bugs in CREATE/DROP INDEX CONCURRENTLY |
Previous Message | Tom Lane | 2012-11-29 04:40:27 | Re: Bugs in CREATE/DROP INDEX CONCURRENTLY |