From: Tom Lane <tgl@sss.pgh.pa.us>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: gnanam@zoniac.com
Cc: pgsql-admin@postgresql.org
Subject: Re: Advise on dropping TEMP table/schema for my use case
Date: Wed, 09 Mar 2011 10:27:58 -0500
Message-ID: <24163.1299684478@sss.pgh.pa.us> (raw)
In-Reply-To: <AANLkTimyDFzfqQ2EVfQi0irjChpLO5Laej8O-aUQ0LR1@mail.gmail.com>
References: <004a01cbde41$a01544a0$e03fcde0$@com>
<AANLkTimyDFzfqQ2EVfQi0irjChpLO5Laej8O-aUQ0LR1@mail.gmail.com>
Scott Marlowe <scott.marlowe@gmail.com> writes:
> On Wed, Mar 9, 2011 at 3:06 AM, Gnanakumar <gnanam@zoniac.com> wrote:
>>
>> So, now we've decided to either DROP TABLE pg_temp_xx.FOO or DROP SCHEMA
>> pg_temp_xx explicitly just before closing the connection (after step 3 and
>> before step 4), so that it'll not be visible for the next database
>> connection request. My question is, which one of the option is recommended
>> and why?
> Why can't you just do:
> DROP TABLE FOO;
Or if you don't want to remember what you've created, update to 8.3+
so you can use DISCARD? (Or really, so that pg_pool can use DISCARD
... it should be the connection pooler's responsibility to ensure that
you get a clean-looking session.)
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, scott.marlowe@gmail.com, gnanam@zoniac.com
Subject: Re: Advise on dropping TEMP table/schema for my use case
In-Reply-To: <24163.1299684478@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox