Re: Patch: show xid and xmin in pg_stat_activity and pg_stat_replication

From: Christian Kruse <christian(at)2ndquadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Patch: show xid and xmin in pg_stat_activity and pg_stat_replication
Date: 2014-01-31 13:02:43
Message-ID: 20140131130243.GA27590@defunct.ch
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

> I suspect we should have a new accessor function that takes a backend
> ID and copies the xid and xmin to pointers provided by the client
> while holding the lock.

what do you think about the approach the attached patch implements?
I'm not really sure if this is what you had in mind, especially if
this is the right lock.

> I also note that the docs seem to need some copy-editing:
>
> + <entry>The current <xref linked="ddl-system-columns">xmin
> value.</xref></entry>

Can you elaborate?

Best regards,

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mitsumasa KONDO 2014-01-31 13:07:59 Re: Add min and max execute statement time in pg_stat_statement
Previous Message Fujii Masao 2014-01-31 12:29:41 Re: pg_basebackup and pg_stat_tmp directory