Re: CREATE DATABASE/DROP DATABASE race conditions - Mailing list pgsql-bugs

From Tom Lane
Subject Re: CREATE DATABASE/DROP DATABASE race conditions
Date
Msg-id 19429.1026666812@sss.pgh.pa.us
Whole thread Raw
In response to CREATE DATABASE/DROP DATABASE race conditions  (Florian Weimer <Weimer@CERT.Uni-Stuttgart.DE>)
Responses Re: CREATE DATABASE/DROP DATABASE race conditions
List pgsql-bugs
Florian Weimer <Weimer@CERT.Uni-Stuttgart.DE> writes:
> I'm observing weird behavior with CREATE DATABASE/DROP DATABASE and
> PostgreSQL 7.2.1 (on Debian/unstable): There seems to be a short time
> period after the 'Z' response of the backend during which the database
> continues to exist (e.g. subsequent CREATE DATABASE operations with
> the same name fail) or does not exist yet (e.g. it is not possible to
> connect to the database).

> You cannot reproduce this with "psql" or "createdb"/"dropdb".

I'm inclined to think it's a bug in your application coding, then.
psql certainly doesn't go out of its way to serialize operations.

Could we see a self-contained test case?

            regards, tom lane

pgsql-bugs by date:

Previous
From: Florian Weimer
Date:
Subject: CREATE DATABASE/DROP DATABASE race conditions
Next
From: Florian Weimer
Date:
Subject: Re: CREATE DATABASE/DROP DATABASE race conditions