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

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: Ricardo Coelho <rcoelho(at)px(dot)com(dot)br>
Cc: pgsql-bugs(at)postgreSQL(dot)org
Subject: Re: [BUGS] General Bug Report: TEMP TABLES becomes permanent CATALOG TABLES
Date: 1999-07-08 03:06:28
Message-ID: 199907080306.XAA23971@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> 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.

This will be fixed in 6.5.1, due out next week.

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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message secret 1999-07-08 14:00:58 Re: [BUGS] General Bug Report: GROUP BY with NULL not done properly(Oracle8& DB/2 do this completely different)
Previous Message Bruce Momjian 1999-07-08 02:53:27 Re: [BUGS] General Bug Report: Files greater than 1 GB are created while sorting