Re: Temp rows - is it possible?

From: Boris Popov <boris(at)procedium(dot)com>
To: Ben <bench(at)silentmedia(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Temp rows - is it possible?
Date: 2003-11-07 23:08:05
Message-ID: 160366638618.20031107150805@procedium.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello Ben,

Friday, November 7, 2003, 2:53:09 PM, you wrote:

B> If the table doesn't have to be 100% accurate, you could always timestamp
B> the rows and have connected clients update their row, while old rows get
B> reaped periodicaly.

I was hoping for a more natural solution. Implementing a heartbeat in
the application is a complication I'd like to avoid at all cost.

-Boris

B> On Fri, 7 Nov 2003, Boris Popov wrote:

>> I do want them to be visible to everybody. This is a sessions pool,
>> where sessions are inserted when our app connects and removed when it
>> disconnects, however this would only work for graceful disconnects,
>> which we all know isn't always the case. So I want a table that is
>> somehow notified of a session disconnect and deletes rows created by
>> that session.
>>
>> Any ideas?

In response to

Browse pgsql-general by date

  From Date Subject
Next Message sgupta5 2003-11-07 23:14:48 regarding constant values
Previous Message Jaime Casanova 2003-11-07 22:59:39 Re: [GENERAL] [HACKERS] retrieve statement from catalogs