Re: using xmin in a query?

From: Tom Lane
Subject: Re: using xmin in a query?
Date: ,
Msg-id: 6688.1311890949@sss.pgh.pa.us
(view: Whole thread, Raw)
In response to: Re: using xmin in a query?  (Michael Nolan)
Responses: Re: using xmin in a query?  (Michael Nolan)
List: pgsql-general

Tree view

using xmin in a query?  (Michael Nolan, )
 Re: using xmin in a query?  (Andy Colson, )
  Re: using xmin in a query?  (Michael Nolan, )
   Re: using xmin in a query?  (Rodrigo Gonzalez, )
 Re: using xmin in a query?  (Tom Lane, )
  Re: using xmin in a query?  (Michael Nolan, )
   Re: using xmin in a query?  (Tom Lane, )
    Re: using xmin in a query?  (Michael Nolan, )
     Re: using xmin in a query?  (Tom Lane, )
      Re: using xmin in a query?  (Michael Nolan, )
       Re: using xmin in a query?  (Tom Lane, )

Michael Nolan <> 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


pgsql-general by date:

From: Tom Lane
Date:
Subject: Re: issue with pg_restore
From: Craig Ringer
Date:
Subject: Re: How to implement autostart of postgres?