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

From Robert Haas
Subject Re: Patch: show xid and xmin in pg_stat_activity and pg_stat_replication
Date
Msg-id CA+TgmoYaDwtvgTcJXEwpbwAnrwYv6Gq00A=ZKjEOjMKe=GT9bg@mail.gmail.com
Whole thread Raw
In response to Patch: show xid and xmin in pg_stat_activity and pg_stat_replication  (Christian Kruse <christian@2ndQuadrant.com>)
Responses Re: Patch: show xid and xmin in pg_stat_activity and pg_stat_replication  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Patch: show xid and xmin in pg_stat_activity and pg_stat_replication  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
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.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Add CREATE support to event triggers
Next
From: Robert Haas
Date:
Subject: Re: Viability of text HISTORY/INSTALL/regression README files (was Re: [COMMITTERS] pgsql: Document a few more regression test hazards.)