Curious buildfarm failures

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Curious buildfarm failures
Дата
Msg-id 6458.1358199348@sss.pgh.pa.us
обсуждение исходный текст
Ответы Re: Curious buildfarm failures  (Andres Freund <andres@2ndquadrant.com>)
Re: Curious buildfarm failures  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Список 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



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: count(*) of zero rows returns 1
Следующее
От: Andres Freund
Дата:
Сообщение: Re: Curious buildfarm failures