* 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..
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2011-04-04 22:43:00|
|Subject: Re: Extensions Dependency Checking |
|Previous:||From: Simon Riggs||Date: 2011-04-04 22:24:15|
|Subject: pgsql: Avoid assuming there will be only 3 states forsynchronous_commi|