Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Re: time table for beta1
On Mon, Apr 4, 2011 at 6:41 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote: > * 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.. 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. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
In response to
- Re: time table for beta1 at 2011-04-04 22:41:59 from Stephen Frost
Responses
- Re: time table for beta1 at 2011-04-04 23:46:08 from Dan Ports
pgsql-hackers by date
Next: From: Robert Haas Date: 2011-04-04 23:10:42 Subject: Re: [COMMITTERS] pgsql: Avoid assuming there will be only 3 states for synchronous_commi Previous: From: Tom Lane Date: 2011-04-04 22:57:30 Subject: Re: Extensions Dependency Checking