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

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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeremy Drake <pgbuildfarm(at)jdrake(dot)com>
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:03:01
Message-ID: 23496.1354161781@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
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.)

			regards, tom lane


In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2012-11-29 04:40:27
Subject: Re: Bugs in CREATE/DROP INDEX CONCURRENTLY
Previous:From: Jeremy DrakeDate: 2012-11-29 03:43:14
Subject: Re: [COMMITTERS] pgsql: Refactor flex and bison make rules

pgsql-committers by date

Next:From: Jeremy DrakeDate: 2012-11-29 04:49:14
Subject: Re: [COMMITTERS] pgsql: Refactor flex and bison make rules
Previous:From: Jeremy DrakeDate: 2012-11-29 03:43:14
Subject: Re: [COMMITTERS] pgsql: Refactor flex and bison make rules

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