| From: | Dan Ports <drkp(at)csail(dot)mit(dot)edu> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | 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-04 23:46:08 |
| Message-ID: | 20110404234608.GB90937@csail.mit.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.. ?Knowing just the pid blows, since the pid could technically
> > end up reused (tho not terribly likely) in the time frame you're trying
> > to figure out what happened during..
>
> 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.
--
Dan R. K. Ports MIT CSAIL http://drkp.net/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2011-04-05 01:09:20 | Re: synchronous_commit and synchronous_replication Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. |
| Previous Message | Robert Haas | 2011-04-04 23:10:42 | Re: [COMMITTERS] pgsql: Avoid assuming there will be only 3 states for synchronous_commi |