On Friday 17 December 2010 7:47:44 am Melvin Davidson wrote: > PostgreSQL 8.3.11 on i686-redhat-linux-gnu, compiled by GCC gcc (GCC) 4.1.2 > 20080704 (Red Hat 4.1.2-46) Linux version 2.6.18-194.26.1.el5 > (mockbuild@xxxxxxxxxxxxxxxxxxxx) (gcc version 4.1.2 20080704 (Red Hat > 4.1.2-48)) #1 SMP Tue Nov 9 12:54:40 EST 2010 > > How is this possible? I've been working as a PostgreSQL DBA for 5 years, > and frankly I'm baffled. > > I had previosly created a TEMP table in a session, but later decided to > make it a permanent table. However, when I attempted to do so, I came > across a very weird problem. PostgreSQL 1st denies that the table exists, > because I do a DROP TABLE IF EXISTS. > But when I do a CREATE TABLE, it says it is already there! > > At first I thought I might have to do with shared_buffer memory. But after > shutting down both the client and server, the problem persists. In fact, I > have even dropped and reloaded the database, and it still occurs. > > Am I missing something obvious? > Or does PostgreSQL have some undocumented, hidden catalog I am not aware of > where it tracks TEMP tables? > Have you tried a REINDEX on pg_class as superuser? -- Adrian Klaver adrian.klaver@xxxxxxxxx -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
