Re: pg_locks view versus prepared transactions

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: pg_locks view versus prepared transactions
Date: 2005-06-20 20:13:39
Message-ID: 22054.1119298419@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> writes:
>> I was also wondering about adding a current-XID column to
>> pg_stat_activity, and encouraging people to join pg_locks and
>> pg_stat_activity on XID instead of PID.

> That would be awesome. Is there any performance penalty to do this?

I gave up on the idea after I realized that current XID tends to change
a lot faster than the pg_stats mechanism is designed to track.
(Consider the half-second lag for starters...) Turning pg_stats into a
realtime mechanism would be horridly expensive.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-06-20 20:18:03 Re: pg_locks view versus prepared transactions
Previous Message Alvaro Herrera 2005-06-20 20:08:43 Re: pg_locks view versus prepared transactions