Delivery-Date: Mon, 25 Oct 93 10:29:33 PDT
Resent-From: postman (POSTGRES mailing list)
Resent-Message-Id: <9310251723.AA19436@postgres.Berkeley.EDU>
Sender: owner-postman@postgres.Berkeley.EDU
Date: Mon, 25 Oct 1993 10:27:53 -0700
From: Kristin Wright <kristin@postgres.Berkeley.EDU>
Message-Id: <199310251727.KAA06704@parkcity.CS.Berkeley.EDU>
To: postgres@postgres.berkeley.edu
Subject: can you reproduce this bug?
Resent-To: postgres-dist
Resent-Date: Mon, 25 Oct 93 10:23:12 PDT


The postgres group has had the following bug reported, but has not
been able to reproduce it and don't know of anyone who has. If _you_
can reproduce the described bug and have some interest in getting it
fixed, please send us mail describing how you reproduce it and any
information relevant to reproducing the bug -- data, queries you use,
postgres version, etc.

Fixing this bug may solve other cache-related postgres bugs. 

Please send any relevant mail to kristin@postgres.Berkeley.EDU.


The bug:
~~~~~~~

When you do a destroydb/createdb using the same database name serially, i.e. 
	
	% destorydb TESTDB
	% createdb TESTDB

and then create a class using a name of a class which was in the old, 
destroyed TESTDB but has not yet been created in the new TESTDB, the
following error occurs:

>  create CLASS (floor = int4)
        StartTransactionCommand() at Mon Oct 25 10:13:13 1993

        ProcessUtility() at Mon Oct 25 10:13:13 1993

WARN:Oct 25 10:13:13:amcreate: CLASS relation already exists
        AbortCurrentTransaction() at Mon Oct 25 10:13:13 1993


The WorkAround
~~~~~~~~~~~~~

Kill & restart the postmaster.