Re: Change behavior of (m)xid_age

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Change behavior of (m)xid_age
Date: 2015-10-23 12:59:35
Message-ID: CAB7nPqSK=kxNYSLiFCybFs1V7eLiYe+OPhTjWrs63u5g6tOL4A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Oct 23, 2015 at 7:20 AM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> Andres Freund wrote:
>
>> FWIW, adding an <> operator for xid seems like a perfectly good idea.

+1. I have wanted that more than once, but avoided it all the time
with some casts.

> +1 (two of them actually --

See for example the attached (do we care about commutativity with int
= xid and int <> xid?).

> (another one for <>(xid,int) which mirrors the =(xid,int) we already have).

To which one are you referring here?
--
Michael

Attachment Content-Type Size
20151023_xidne.patch application/x-patch 4.8 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2015-10-23 15:16:55 Re: Making tab-complete.c easier to maintain
Previous Message Robert Haas 2015-10-23 12:29:59 Re: Multiline-statement and multi-statement for pgbench custom script.