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) o
Florian Weimer <[EMAIL PROTECTED]> 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 CR
Tom Lane <[EMAIL PROTECTED]> writes:
>> You cannot reproduce this with "psql" or "createdb"/"dropdb".
>
> I'm inclined to think it's a bug in your application coding, then.
Well, sort of.
> psql certainly doesn't go out of its way to serialize operations.
Well, unless you play around with \con
Florian Weimer <[EMAIL PROTECTED]> writes:
> \connect template1 fw
> CREATE DATABASE aaa;
> \connect aaa fw;
> CREATE TABLE a (a text);
> \connect template1 fw
> DROP DATABASE aaa;
> sometimes results in:
> You are now connected to database template1 as user fw.
> CREATE DATABASE aaa;
> CREATE D
