From: | Michael Nolan <htfoot(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: using xmin in a query? |
Date: | 2011-07-28 22:20:24 |
Message-ID: | CAOzAquK18WXfcKPdboxU1mWfn4NskaYCYGiofaVhyJzm2nx8zw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Jul 28, 2011 at 5:09 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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?
>
I'm not sure yet. I was doing some thinking about ways to do incremental
backups
(at least for inserted/updated rows, deleted rows present a different
challenge),
and was just doing some simple queries to see what worked and what didn't..
It also appears you cannot group on a column of type xid.
Would adding a <> operator enable that?
--
Mike Nolan
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-07-28 22:36:42 | Re: using xmin in a query? |
Previous Message | Tom Lane | 2011-07-28 22:09:09 | Re: using xmin in a query? |