From: | "Ross J(dot) Reedstrom" <reedstrm(at)wallace(dot)ece(dot)rice(dot)edu> |
---|---|
To: | pgsql-sql(at)postgreSQL(dot)org |
Subject: | Re: [SQL] MVCC and concurrent clients |
Date: | 1999-07-31 23:05:16 |
Message-ID: | 19990731180516.A16854@wallace.ece.rice.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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_table
WHERE 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(at)rice(dot)edu>
NSBRI Research Scientist/Programmer
Computer and Information Technology Institute
Rice University, 6100 S. Main St., Houston, TX 77005
From | Date | Subject | |
---|---|---|---|
Next Message | Stéphane FILLON | 1999-08-01 05:31:38 | DOMAIN DEFINITION |
Previous Message | Stéphane FILLON | 1999-07-31 22:13:44 | Tr: DUMP database for sample |