pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Viorel Dragomir <bigchief@vio.ro>
Cc: pgsql-sql@postgresql.org
Subject: Re: summing tables
Date: Tue, 15 Jul 2003 11:42:03 -0400
Message-ID: <22931.1058283723@sss.pgh.pa.us> (raw)
In-Reply-To: <012b01c34ae6$40ab0870$0600a8c0@fix.ro>
References: <20030715140921.7c5a6a6c.erik@thiele-hydraulik.de>
	<001501c34aca$e70ca280$0600a8c0@fix.ro>
	<20030715143925.54716ed4.erik@thiele-hydraulik.de>
	<22671.1058282096@sss.pgh.pa.us>
	<012b01c34ae6$40ab0870$0600a8c0@fix.ro>

"Viorel Dragomir" <bigchief@vio.ro> writes:
> Indeed it was a mistake not to put the table_name. in where clause.
> But this doesn't resolve the problem.

> Do you know in which order the update will modify the rows?

No, and *it does not matter*.  You are forgetting that this all runs
under MVCC rules.  The sub-SELECTs will see the pre-existing versions
of the rows, whether or not the UPDATE has yet produced new versions.

			regards, tom lane

view thread (13+ messages)  latest in thread

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

copy link · copy postgr.es

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 using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, bigchief@vio.ro
  Subject: Re: summing tables
  In-Reply-To: <22931.1058283723@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