Re: upgraded to 7.3.2 and now see pg_temp_x databases?

From: "Patrick Hatcher" <PHatcher(at)macys(dot)com>
To: "Tom Lane <tgl" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: upgraded to 7.3.2 and now see pg_temp_x databases?
Date: 2003-03-21 20:11:19
Message-ID: OFC4315607.0C1079DD-ON88256CF0.006EDA69-88256CF0.006F50A0@fds.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


Thank you for the clarification.

Patrick Hatcher


Tom Lane
<tgl(at)sss(dot)pgh(dot)p To: "Patrick Hatcher" <PHatcher(at)macys(dot)com>
a.us> cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] upgraded to 7.3.2 and now see pg_temp_x
03/21/2003 databases?
11:40 AM

"Patrick Hatcher" <PHatcher(at)macys(dot)com> writes:
> I upgraded from 7.2 to 7.3.2 and everything works great. However, when I
> open pgAdminII, I see three empty databases named pg_temp_2,pg_temp_4
and
> pg_temp_8. What are these, and are they safe to remove?

Those are schemas, not databases; they are created to hold temp tables.
While you can remove 'em if you wish (and if they're currently empty;
don't do a DELETE CASCADE!), there's no point in it, because they'll be
recreated as soon as backends need to make temp tables.

An empty schema doesn't cost anything except one row in pg_namespace,
so it didn't seem worthwhile to remove the schema only to have to make
it again later. Instead, empty temp schemas are left around for re-use
by future backends.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Guillaume Houssay 2003-03-21 20:22:17 configuration according to the database
Previous Message Tom Lane 2003-03-21 19:40:33 Re: upgraded to 7.3.2 and now see pg_temp_x databases?