Re: Persistent data per connection

From: Jeff Amiel <jamiel(at)istreamimaging(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Persistent data per connection
Date: 2005-03-25 16:56:50
Message-ID: 424442D2.5010207@istreamimaging.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)istreamimaging(dot)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
>
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Joshua D. Drake 2005-03-25 17:23:53 Re: Persistent data per connection
Previous Message Thomas F.O'Connell 2005-03-25 16:51:45 Re: Referential integrity using constant in foreign key