Denis Gasparin wrote:
> Martijn van Oosterhout ha scritto:
>> On Thu, Jun 28, 2007 at 11:12:19AM +0100, Bruce McAlister wrote:
>>
>>> I just want to verify that I understand you correctly here, do you mean
>>> that the temporary table is created by specific sql, for example, create
>>> temp table, then perform some actions on that temp table, then, either
>>> you remove the temp table, or, if you close the session/connection the
>>> postmaster will clean up the temp table? What happens if you're using
>>> connection pools, i mean are those sessions deemed "closed" after the
>>> queries complete, when the pool connections are persistent.
>>>
>>
>> Yes, the temp table is private to the session and will be removed once
>> the session closes, if not sooner. As for connection pools, IIRC there
>> is a RESET SESSION command which should also get rid of the temporary
>> tables.
>>
> RESET SESSION command is available only in 8.2 branch, isn't it?
> I tried to issue the command in a 8.1 server and the answer was: ERROR:
> unrecognized configuration parameter "session"
>
I had a look in our configuration and there is a "session" option that
comes up if you type "RESET " and press TAB twice. However, if you do
try to run it, it comes back with:
blueface-crm=# RESET session ;
ERROR: unrecognized configuration parameter "session"
We're running PostgreSQL 8.2.4. Alvaro said it was only going to be
available in 8.3. I hope they backport it to 8.2 though, 90% of our
connections are via connection pooled drivers, so being able to reset
the session after each transaction would be a handy way to ensure the
environment is sane for the next transaction :)
> Is there available a patch for the 8.1 version of postgresql?
>
> Thank you,
> Denis
