Horton

Thread

  1. General Bug Report: TEMP TABLES becomes permanent CATALOG TABLES

    Unprivileged user <nobody> — 1999-07-01T22:20:04Z

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

--------------------------------------------------------------------------

Solution:
---------


--------------------------------------------------------------------------