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

Curious buildfarm failures

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgreSQL(dot)org
Subject: Curious buildfarm failures
Date: 2013-01-14 21:35:48
Message-ID: 6458.1358199348@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Since commit 2065dd2834e832eb820f1fbcd16746d6af1f6037, there have been
a few buildfarm failures along the lines of
  
  -- Commit table drop
  COMMIT PREPARED 'regress-two';
! PANIC:  failed to re-find shared proclock object
! PANIC:  failed to re-find shared proclock object
! connection to server was lost

Evidently I bollixed something, but what?  I've been unable to reproduce
this locally so far.  Anybody see what's wrong?

Another thing is that dugong has been reproducibly failing with

 drop cascades to table testschema.atable
  -- Should succeed
  DROP TABLESPACE testspace;
+ ERROR:  tablespace "testspace" is not empty

since the elog-doesn't-return patch (b853eb97) went in.  Maybe this is
some local problem there but I'm suspicious that there's a connection.
But what?

Any insights out there?

			regards, tom lane


Responses

pgsql-hackers by date

Next:From: Andres FreundDate: 2013-01-14 21:50:16
Subject: Re: Curious buildfarm failures
Previous:From: Tom LaneDate: 2013-01-14 21:15:36
Subject: Re: count(*) of zero rows returns 1

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