From: Ross J. Reedstrom <reedstrm@wallace.ece.rice.edu>
To: pgsql-sql@postgreSQL.org
Subject: Re: [SQL] MVCC and concurrent clients
Date: Sat, 31 Jul 1999 18:05:16 -0500
Message-ID: <19990731180516.A16854@wallace.ece.rice.edu> (raw)
In-Reply-To: <12132.933365440@sss.pgh.pa.us>
References: <12132.933365440@sss.pgh.pa.us>
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@rice.edu>
NSBRI Research Scientist/Programmer
Computer and Information Technology Institute
Rice University, 6100 S. Main St., Houston, TX 77005
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: reedstrm@wallace.ece.rice.edu
Subject: Re: [SQL] MVCC and concurrent clients
In-Reply-To: <19990731180516.A16854@wallace.ece.rice.edu>
References: <12132.933365440@sss.pgh.pa.us> <19990731180516.A16854@wallace.ece.rice.edu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox