I have rebuild the filesystem on my indy (MIPS) that Andrew reported on. The first run completed 100%, I would give
it a couple more runs before we can say its the filesystem not Postgresql that was causing the drop to fail.
---------- Original Message -----------
From: Andrew Dunstan <andrew@dunslane.net>
To: jim@buttafuoco.net
Sent: Wed, 15 Dec 2004 16:42:59 -0500
Subject: [Fwd: Re: [HACKERS] race condition for drop schema cascade?]
> Jim, please advise?
>
> thanks
>
> andrew
>
> -------- Original Message --------
> Subject: Re: [HACKERS] race condition for drop schema cascade?
> Date: Wed, 15 Dec 2004 16:29:01 -0500
> From: Tom Lane <tgl@sss.pgh.pa.us>
> To: Andrew Dunstan <andrew@dunslane.net>
> CC: PostgreSQL-development <pgsql-hackers@postgresql.org>
> References: <41C0A720.9050803@dunslane.net>
>
> Andrew Dunstan <andrew@dunslane.net> writes:
> > I have seen this failure several times, but not consistently, on the
> > buildfarm member otter (Debian/MIPS) and possible on others, and am
> > wondering if it indicates a possible race condition on DROP SCHEMA CASCADE.
>
> Hard to see what, considering that there's only one backend touching
> that tablespace in the test. I'd be inclined to wonder if there's
> a filesystem-level problem on that platform. What filesystem are you
> running on anyway?
>
> regards, tom lane
------- End of Original Message -------
