Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6]) by hub.org (8.9.3/8.9.3) with ESMTP id RAA63149 for ; Thu, 27 May 1999 17:38:26 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id RAA23672; Thu, 27 May 1999 17:37:52 -0400 (EDT) To: Alex Turner , "pgsql-interfaces@postgreSQL.org" Subject: Re: [INTERFACES] Wierd error when creating a table... In-reply-to: Your message of Thu, 27 May 1999 16:54:52 -0400 <23539.927838492@sss.pgh.pa.us> Date: Thu, 27 May 1999 17:37:52 -0400 Message-ID: <23670.927841072@sss.pgh.pa.us> From: Tom Lane I wrote: > That's a bug: the physical file for the relation has already been > created by the time the failure in creating the index occurs, and > although all the updates to system tables get backed out, the empty > file is not removed during the transaction abort. After further investigation, the above is wrong, or at least obsolete: the physical file for the table that couldn't be created *is* removed when the transaction is cleaned up. (At least it is in current 6.5 code; didn't try older versions.) There's still a bug though --- apparently the system still has an entry for the failed table in its "relation cache", and that prevents a subsequent CREATE TABLE for the same table name from succeeding. A workaround is to exit your psql session and start a new one; the new backend won't have the erroneous cache entry. This needs to be fixed though. regards, tom lane