Re: [SQL] MVCC and concurrent clients - Mailing list pgsql-sql

From Ross J. Reedstrom
Subject Re: [SQL] MVCC and concurrent clients
Date
Msg-id 19990731180516.A16854@wallace.ece.rice.edu
Whole thread Raw
In response to MVCC and concurrent clients  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [SQL] MVCC and concurrent clients
Re: [SQL] MVCC and concurrent clients
List pgsql-sql
On Fri, Jul 30, 1999 at 04:10:40PM -0400, Tom Lane wrote:
Tom - 
How about timestamps?

> something like this:
>     BEGIN TRANSACTION;
>     INSERT and/or UPDATE, setting each new or modified    row's updatedTime to 'now';
>     NOTIFY shared_table;
>     END TRANSACTION;
> 
> All clients are listeners for the NOTIFY messages, and whenever
> a notify is received, a client will do
>     SELECT * FROM shared_tableWHERE updateTime >= last_time_looked;

> 
> Alternatively, is there a better way to design the table structure for
> this application?  I would think "give me all recently modified tuples"
> is a pretty standard problem.
> 

Ross
-- 
Ross J. Reedstrom, Ph.D., <reedstrm@rice.edu> 
NSBRI Research Scientist/Programmer
Computer and Information Technology Institute
Rice University, 6100 S. Main St.,  Houston, TX 77005


pgsql-sql by date:

Previous
From: "Stéphane FILLON"
Date:
Subject: Tr: DUMP database for sample
Next
From: "Stéphane FILLON"
Date:
Subject: DOMAIN DEFINITION