Re: Need Multixact Freezing Docs

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Need Multixact Freezing Docs
Date: 2014-09-10 21:13:18
Message-ID: 20140910211318.GD21173@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Sep 5, 2014 at 07:39:36PM -0400, Bruce Momjian wrote:
> On Wed, Sep 3, 2014 at 05:17:17PM -0400, Robert Haas wrote:
> > > I had a look at this and came upon a problem --- there is no multi-xid
> > > SQL data type, and in fact the system catalogs that store mxid values
> > > use xid, e.g.:
> > >
> > > relminmxid | xid | not null
> > >
> > > With no mxid data type, there is no way to do function overloading to
> > > cause age to call the mxid variant.
> > >
> > > Should we use an explicit mxid_age() function name? Add an mxid data
> > > type?
> >
> > Maybe both. But mxid_age() is probably the simpler way forward just to start.
>
> OK, patch applied using mxid_age() and no new data type.

Applied.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Vik Fearing 2014-09-10 21:43:30 Re: [BUGS] BUG #10823: Better REINDEX syntax.
Previous Message Tomas Vondra 2014-09-10 21:09:54 Re: bad estimation together with large work_mem generates terrible slow hash joins