| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dan Ports <drkp(at)csail(dot)mit(dot)edu> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: time table for beta1 |
| Date: | 2011-04-05 14:31:54 |
| Message-ID: | 2606.1302013914@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dan Ports <drkp(at)csail(dot)mit(dot)edu> writes:
> On Mon, Apr 04, 2011 at 07:04:59PM -0400, Robert Haas wrote:
>> On Mon, Apr 4, 2011 at 6:41 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
>>> What'd be horribly useful would be the pid and the *time* that the lock
>>> was taken.
>> Well, I don't think we're likely to redesign pg_locks at this point,
>> so it's a question of making the best use of the fields we have to
>> work with.
> Agreed. Note that the vxid of the transaction that took the lock is
> included in there, so that's at least something you could correlate
> with a logfile.
Another problem is that supporting that would imply injecting
gettimeofday() into the lock-acquisition sequence, and that's pretty
damn expensive on some platforms.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2011-04-05 14:49:37 | Re: Set hint bits upon eviction from BufMgr |
| Previous Message | Robert Haas | 2011-04-05 14:13:54 | Re: Open issues for collations |