Re: [BUGS] General Bug Report: TEMP TABLES becomes permanent CATALOG TABLES

>
> ============================================================================
>                         POSTGRESQL BUG REPORT TEMPLATE
> ============================================================================
>
>
> Your name               : Ricardo Coelho
> Your email address      : rcoelho@px.com.br
>
> Category                : runtime: back-end
> Severity                : serious
>
> Summary: TEMP TABLES becomes permanent CATALOG TABLES
>
> System Configuration
> --------------------
>   Operating System   : RedHat Linux 5.2 Intel
>
>   PostgreSQL version : 6.5
>
>   Compiler used      : gcc
>
> Hardware:
> ---------
> Pentium II 350MHz 128M RAM
>
> Versions of other tools:
> ------------------------
>
>
> --------------------------------------------------------------------------
>
> Problem Description:
> --------------------

> When you execute a wrong SQL command after create a TEMP TABLE,
postgres backend doesn't drop this table after connection ends. We can't
drop pg_temp.PID.N with "drop table" command because it is a system
catalog table. So, we had to dumpall the database, edit db.out file to
erase lines of pg_temp??? create table and reload it again.

>
> --------------------------------------------------------------------------
>
> Test Case:
> ----------
> psql mydb
> mydb=> select * into temp table TMP from anytable;
> mydb=> drop table invalidTable;
> mydb=> \q
> psql mydb
> mydb=> \dS    --> You will see a new permanent system table.

I can confirm that this a bug.  I am looking at it now.  As a
workaround, you can delete the temp tables by starting a postgres
backend with the -O flag to allow system table modifications, and
droping the table.

--
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026