pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ross J. Reedstrom <reedstrm@wallace.ece.rice.edu>
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [SQL] MVCC and concurrent clients
Date: Sun, 01 Aug 1999 10:55:30 -0400
Message-ID: <28386.933519330@sss.pgh.pa.us> (raw)
In-Reply-To: <19990731180516.A16854@wallace.ece.rice.edu>

"Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu> writes:
> How about timestamps?

I thought about that approach originally, but it doesn't change the
nature of the problem.  Transactions will not necessarily commit in
the same order as the timestamps they've applied to updated tuples.

			regards, tom lane



view thread (4+ messages)  latest in thread

Message-ID: <28386.933519330@sss.pgh.pa.us>
Permalink:  ../28386.933519330@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/28386.933519330@sss.pgh.pa.us

 · 

reply

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: tgl@sss.pgh.pa.us, reedstrm@wallace.ece.rice.edu
  Subject: Re: [SQL] MVCC and concurrent clients
  In-Reply-To: <28386.933519330@sss.pgh.pa.us>
  References: <19990731180516.A16854@wallace.ece.rice.edu> <28386.933519330@sss.pgh.pa.us>

* 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