pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: george young <gry@ll.mit.edu>
To: pgsql-sql@postgresql.org
Subject: Re: tid_le comparison for tuple id (ctid) values?
Date: Mon, 21 Nov 2005 20:35:27 -0500
Message-ID: <20051121203527.5378122b.gry@ll.mit.edu> (raw)
In-Reply-To: <4271.1132607968@sss.pgh.pa.us>
References: <20051121160016.282c66c2.gry@ll.mit.edu>
	<4271.1132607968@sss.pgh.pa.us>

On Mon, 21 Nov 2005 16:19:28 -0500
Tom Lane <tgl@sss.pgh.pa.us> threw this fish to the penguins:

> george young <gry@ll.mit.edu> writes:
> >    update steps set x=x||'X' from steps s where steps.key1=s.key1 and steps.key2=s.key2 and step.ctid<s.ctid;
> 
> > But this fails because there is no less-than operator (or function) on
> > type "tid".
> 
> Probably a good thing, too, since if there was it wouldn't have anything
> reliable to do with the age of the tuple.

Well, I don't have any need for it to correlate with the age of the
tuple.  My use of step.ctid<s.ctid was not to get the earliest or
latest row, but just to *choose* one.  Perhaps there's some other
query that would modify only one of each pair of equal-keyed rows?

-- George
-- 
"Are the gods not just?"  "Oh no, child.
What would become of us if they were?" (CSL)



view thread (5+ messages)  latest in thread

Message-ID: <20051121203527.5378122b.gry@ll.mit.edu>
Permalink:  ../20051121203527.5378122b.gry@ll.mit.edu/
Also on:    postgresql.org/message-id/20051121203527.5378122b.gry@ll.mit.edu

 · 

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: gry@ll.mit.edu
  Subject: Re: tid_le comparison for tuple id (ctid) values?
  In-Reply-To: <20051121203527.5378122b.gry@ll.mit.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