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

Re: [COMMITTERS] pgsql: Refactor flex and bison make rules

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 (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-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.



In response to

pgsql-hackers by date

Next:From: Pavan DeolaseeDate: 2012-11-29 04:50:12
Subject: Re: Bugs in CREATE/DROP INDEX CONCURRENTLY
Previous:From: Tom LaneDate: 2012-11-29 04:40:27
Subject: Re: Bugs in CREATE/DROP INDEX CONCURRENTLY

pgsql-committers by date

Next:From: Tom LaneDate: 2012-11-29 15:38:10
Subject: pgsql: Fix assorted bugs in CREATE/DROP INDEX CONCURRENTLY.
Previous:From: Tom LaneDate: 2012-11-29 04:03:01
Subject: Re: [COMMITTERS] pgsql: Refactor flex and bison make rules

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