Skip site navigation (1) Skip section navigation (2)

Re: time table for beta1

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>,Dan Ports <drkp(at)csail(dot)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: time table for beta1
Date: 2011-04-04 22:41:59
Message-ID: 20110404224159.GB4548@tamriel.snowman.net (view raw or flat)
Thread:
Lists: pgsql-hackers
* Robert Haas (robertmhaas(at)gmail(dot)com) wrote:
> Well, the flip side is that if you have appropriate logging turned on,
> you might be able to go back and look at what the transaction that
> took the lock actually did, which won't be possible if you arbitrarily
> throw the PID away.

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..

	Thanks,

		Stephen

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2011-04-04 22:43:00
Subject: Re: Extensions Dependency Checking
Previous:From: Simon RiggsDate: 2011-04-04 22:24:15
Subject: pgsql: Avoid assuming there will be only 3 states forsynchronous_commi

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group