From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
Cc: | math(at)sai(dot)msu(dot)ru, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: Curious buildfarm failures |
Date: | 2013-01-15 16:19:28 |
Message-ID: | 26804.1358266768@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andres Freund <andres(at)2ndquadrant(dot)com> writes:
>>> On 2013-01-14 16:35:48 -0500, Tom Lane wrote:
>>>> 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?
> Do you have idea whats going on? I don't really have any clue other than
> guessing it might be an compiler bug.
I'm suspicious of that too, but it's hard to see why it would manifest
like this while everything else appears to be fine. A codegen bug
triggered by elog ought to show up in a lot of places, one would think.
> Could the buildfarm owner perhaps tell us which files are left in the
> tablespace 'testspace'?
I'm betting the answer is "none", and that what's happening is some sort
of timing problem (ie, the DROP TABLESPACE somehow isn't waiting for the
checkpointer process to clean out all the just-dropped files). The
PANIC at shutdown looks like it might be some sort of doppelganger of
the same bug, ie dropped table cleaned out too early.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2013-01-15 16:23:22 | Re: logical changeset generation v4 |
Previous Message | Tom Lane | 2013-01-15 16:10:22 | Re: logical changeset generation v4 |