Re: using xmin in a query?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Nolan <htfoot(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: using xmin in a query?
Date: 2011-07-28 22:09:09
Message-ID: 6688.1311890949@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Michael Nolan <htfoot(at)gmail(dot)com> writes:
> It seems like we're being inconsistent here in allowing 'where xid =
> integer' but not allowing 'where xid != integer'.

Well, if you look into pg_operator you'll soon find that there are
exactly two built-in operators that accept type xid: "=(xid,xid)" and
"=(xid,integer)" (where I'd say the latter is just a kluge).
There hasn't previously been any demand to flesh it out more than that.
Do you have an actual use-case where <> would be helpful, or is this
just experimentation?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael Nolan 2011-07-28 22:20:24 Re: using xmin in a query?
Previous Message Michael Nolan 2011-07-28 21:55:31 Re: using xmin in a query?