Re: Patch: show xid and xmin in pg_stat_activity and pg_stat_replication - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Patch: show xid and xmin in pg_stat_activity and pg_stat_replication
Date
Msg-id 20140206085859.GJ28649@alap3.anarazel.de
Whole thread Raw
In response to Re: Patch: show xid and xmin in pg_stat_activity and pg_stat_replication  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 2014-02-05 13:26:15 -0500, Robert Haas wrote:
> On Wed, Feb 5, 2014 at 1:21 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > Robert Haas <robertmhaas@gmail.com> writes:
> >> It feels weird to me that the new columns are called transactionid and
> >> xmin.  Why not xid and xmin?
> >
> > Actually the part of that that bothers me is "xmin", which conflicts
> > with a reserved system column name.  While you can legally pick such
> > conflicting names for view columns, it's not going to be so much fun
> > when you try to join that view against some regular table.
> 
> That's a fair point, too.  So maybe we should go with something like
> backend_xid and backend_xmin or some other prefix that we come up
> with.  My concern is more that I think they should be consistent
> somehow.

Those work for me.

We have a bit of a confusing situation atm, pg_prepared_xact calls it's
xid transaction, pg_locks transactionid... So if we add a new speling,
we should like it sufficiently to use it in the future.

Greetings,

Andres Freund

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Yeb Havinga
Date:
Subject: Re: Row-security on updatable s.b. views
Next
From: Christoph Berg
Date:
Subject: Re: [doc patch] extra_float_digits and casting from real to numeric