Skip site navigation (1) Skip section navigation (2)

Drop does not always drop

From: Bruce Badger <bbadger(at)openskills(dot)com>
To: pgsql-novice(at)postgresql(dot)org
Subject: Drop does not always drop
Date: 2004-12-20 04:01:50
Message-ID: 1103515310.2868.53.camel@orac.set.badgerse.com (view raw or flat)
Thread:
Lists: pgsql-novice
I'm building a system in Smalltalk and using unit tests (SUnit)
extensively.  The unit tests cover all model and persistence aspects of
the system, and part of what they do is create and drop the tables in
the system for each bunch of tests.  So, tables are being rapidly
created and dropped.

Sometimes, the drops don't work, and I get errors when I try and create
the tables again like:

Error message: ERROR:  relation "member_member_id_seq" already exists

or:

Error message: ERROR:  duplicate key violates unique constraint
"pg_class_relname_nsp_index"

Note that if I run the *same unit tests* 10 time in a row (just hitting
the "test" button in the SUnit UI 10 times), 2 or 3 iterations of the
tests will fail with one of the above messages.  All the other tests
work as expected - the dropped tables are dropped and stay dropped.

I have a complete log of a session which demonstrates all three
situation (works, "already exists" and "duplicate key").  This log is
from the Smalltalk PostgreSQL driver and shows all the messages passed
between my Smalltalk image and the PostgreSQL backend.  I've not posted
the log here because it's 40k, but here are some snippets:

In some cases, the deletes look like this in the log (in others a
transaction is started and committed):

December 19, 2004 19:17:40.533
<<<<<	ReadyForQueryMessage

December 19, 2004 19:17:40.533
>>>>>	QueryMessage
'drop table member'

December 19, 2004 19:17:40.540
<<<<<	CompletedResponseMessage
Command tag: DROP TABLE

December 19, 2004 19:17:40.540
<<<<<	ReadyForQueryMessage

December 19, 2004 19:17:40.540
>>>>>	QueryMessage
'drop table email_address'

December 19, 2004 19:17:40.545
<<<<<	CompletedResponseMessage
Command tag: DROP TABLE

Here are two tables being created OK:

December 19, 2004 19:17:40.545
<<<<<	ReadyForQueryMessage

December 19, 2004 19:17:40.545
>>>>>	QueryMessage
'create table member (
	member_id serial primary key,
	member_number integer)'

December 19, 2004 19:17:40.546
<<<<<	NoticeResponseMessage
Message: NOTICE:  CREATE TABLE will create implicit sequence
"member_member_id_seq" for "serial" column "member.member_id"

December 19, 2004 19:17:40.546
>>>>>	QueryMessage
'create table email_address (
	email_address_id serial primary key,
	email_address_string text)'

December 19, 2004 19:17:40.547
<<<<<	NoticeResponseMessage
Message: NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index
"member_pkey" for table "member"

Here is the "already exists" (remember, this happens after an apparently
successful drop):

December 19, 2004 19:17:32.006
<<<<<	ReadyForQueryMessage

December 19, 2004 19:17:32.006
>>>>>	QueryMessage
'create table member (
	member_id serial primary key,
	member_number integer)'

December 19, 2004 19:17:32.007
<<<<<	NoticeResponseMessage
Message: NOTICE:  CREATE TABLE will create implicit sequence
"member_member_id_seq" for "serial" column "member.member_id"

December 19, 2004 19:17:32.007
<<<<<	NoticeResponseMessage
Message: NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index
"member_pkey" for table "member"

December 19, 2004 19:17:32.047
<<<<<	ErrorResponseMessage
Error message: ERROR:  relation "member_member_id_seq" already exists

And here is a sequence ending with a duplicate key violation (again, the
drops worked fine.):

December 19, 2004 19:17:40.577
<<<<<	ReadyForQueryMessage

December 19, 2004 19:17:40.577
>>>>>	QueryMessage
'create table member (
	member_id serial primary key,
	member_number integer)'

December 19, 2004 19:17:40.578
<<<<<	NoticeResponseMessage
Message: NOTICE:  CREATE TABLE will create implicit sequence
"member_member_id_seq" for "serial" column "member.member_id"

December 19, 2004 19:17:40.578
<<<<<	NoticeResponseMessage
Message: NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index
"member_pkey" for table "member"

December 19, 2004 19:17:40.617
<<<<<	ErrorResponseMessage
Error message: ERROR:  duplicate key violates unique constraint
"pg_class_relname_nsp_index"


It's worrying that sometimes this works, and sometimes it does not.

Does anyone have any ideas what I'm getting wrong here?

Thanks,
	Bruce
-- 
Make the most of your skills - with OpenSkills
http://www.openskills.com



Responses

pgsql-novice by date

Next:From: Gino LucreziDate: 2004-12-20 11:40:45
Subject: Re: how to echo SQL commands in the output of a script
Previous:From: A GilmoreDate: 2004-12-20 02:34:45
Subject: Re: Querying now()

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group