| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Christian Kruse <christian(at)2ndquadrant(dot)com> |
| Cc: | 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-29 20:11:38 |
| Message-ID: | CA+U5nML+4wHCYD8i29Nhh8ozFTpsvsrzLa3XFp67bfCrZxjV8Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 14 January 2014 08:38, Christian Kruse <christian(at)2ndquadrant(dot)com> wrote:
> Hi,
>
> On 13/01/14 20:06, Heikki Linnakangas wrote:
>> On 12/17/2013 04:58 PM, Christian Kruse wrote:
>> >attached you will find a patch for showing the current transaction id
>> >(xid) and the xmin of a backend in pg_stat_activty and the xmin in
>> >pg_stat_replication.
>>
>> Docs.
>
> Thanks, update with updated docs is attached.
Looks simple enough and useful for working out which people are
holding up CONCURRENT activities.
I've not been involved with this patch, so any objections to me doing
final review and commit?
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Karlsson | 2014-01-29 20:13:28 | Re: Planning time in explain/explain analyze |
| Previous Message | Josh Berkus | 2014-01-29 20:07:47 | Re: Add min and max execute statement time in pg_stat_statement |