Wait i did the following test: SELECT count(*) from pg_class ; count ------- 894
SELECT count(*) from pg_attribute ; count ------- 7264 CREATE temp table temp_test (id integer); CREATE TABLE SELECT count(*) from pg_class ; count ------- 895 SELECT count(*) from pg_attribute ; count ------- 7272 I DISCONNECTED AND RECONNECTED TO THE DATABASE: NOW SELECT count(*) from pg_class ; count ------- 894 SELECT count(*) from pg_attribute ; count ------- 7264 According to those results the meta_data for a temp table are automatically removed when the table is destroyed So ........ ----- Original Message ----- From: "Nagib Abi Fadel" <[EMAIL PROTECTED]> To: "Manfred Koizar" <[EMAIL PROTECTED]> Cc: "Mike Mascari" <[EMAIL PROTECTED]>; "Bruce Momjian" <[EMAIL PROTECTED]>; "generalpost" <[EMAIL PROTECTED]> Sent: Friday, June 04, 2004 11:14 AM Subject: Re: [GENERAL] Creating a session variable in Postgres > So considering those facts, it would be better to use the Sequence Method, > since it would only require cleaning up one table .... > Or is there anything else i am missing ??? > > > ----- Original Message ----- > From: "Manfred Koizar" <[EMAIL PROTECTED]> > To: "Nagib Abi Fadel" <[EMAIL PROTECTED]> > Cc: "Mike Mascari" <[EMAIL PROTECTED]>; "Bruce Momjian" > <[EMAIL PROTECTED]>; "generalpost" <[EMAIL PROTECTED]> > Sent: Friday, June 04, 2004 08:32 AM > Subject: Re: [GENERAL] Creating a session variable in Postgres > > > > On Fri, 4 Jun 2004 08:25:38 +0200, "Nagib Abi Fadel" > > <[EMAIL PROTECTED]> wrote: > > >The use of sequence would require to clean up the table every N hour . > > > > Right. > > > > >The use of temporary table wouldn't require any cleanup. > > > > Wrong. You would have to clean up the meta data, at least pg_class and > > pg_attribute, maybe pg_index also. For the price of one temp table you > > can have several rows in a permanent table. > > > > Servus > > Manfred > ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html