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@momjian.us> http://momjian.us EnterpriseDB
http://enterprisedb.com
+ Everyone has their own god. +