Re: Persistent data per connection - Mailing list pgsql-general

From Jeff Amiel
Subject Re: Persistent data per connection
Date
Msg-id 424442D2.5010207@istreamimaging.com
Whole thread Raw
In response to Re: Persistent data per connection  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Persistent data per connection  (Steve Atkins <steve@blighty.com>)
List pgsql-general
because the connection is never really dropped...
using a connection pool....so it's just reclaimed by the pool on a
connection.close() or after a  timeout  period

Tom Lane wrote:

>Jeff Amiel <jamiel@istreamimaging.com> writes:
>
>
>>We've been struggling for several days now to come up with a mechanism
>>that allows us to establish a mechanism to store data that remains
>>persistent for the life of the connection.
>>
>>
>
>Why don't you just store it in a temporary table?  Goes away at
>connection drop by definition ... and each connection can use the same
>name for the temp table, so coding is easy.
>
>            regards, tom lane
>
>


pgsql-general by date:

Previous
From: Thomas F.O'Connell
Date:
Subject: Re: Referential integrity using constant in foreign key
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Persistent data per connection