| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Florian Weimer <Weimer(at)CERT(dot)Uni-Stuttgart(dot)DE> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: CREATE DATABASE/DROP DATABASE race conditions |
| Date: | 2002-07-14 17:13:32 |
| Message-ID: | 19429.1026666812@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Florian Weimer <Weimer(at)CERT(dot)Uni-Stuttgart(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florian Weimer | 2002-07-14 17:53:08 | Re: CREATE DATABASE/DROP DATABASE race conditions |
| Previous Message | Florian Weimer | 2002-07-14 14:18:52 | CREATE DATABASE/DROP DATABASE race conditions |