Re: pg_locks needs a facelift - Mailing list pgsql-hackers

From Jim C. Nasby
Subject Re: pg_locks needs a facelift
Date
Msg-id 20050504040230.GT47820@decibel.org
Whole thread Raw
In response to Re: pg_locks needs a facelift  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, May 03, 2005 at 11:43:41PM -0400, Tom Lane wrote:
> "Jim C. Nasby" <decibel@decibel.org> writes:
> > I wish you wouldn't since http://rrs.decibel.org uses it.
> 
> Don't worry, I'll veto any immediate removal of functionality ;-)

Yes, but will core (or worse, that Bruce guy) over-ride your veto? ;P

> The correct way to handle this is to add some better userlock
> functionality and deprecate what's there.  We can remove the crufty
> stuff in a release or three after it's been officially deprecated
> ... but there is no reason to remove it immediately.  It won't conflict
> with a better version, just exist alongside.

Hopefully by then I'll have come up with a reason not to support
pre-8.whenever_userlock_is_improved. :)
-- 
Jim C. Nasby, Database Consultant               decibel@decibel.org 
Give your computer some brain candy! www.distributed.net Team #1828

Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: A proper fix for the conversion-function problem
Next
From: Josh Berkus
Date:
Subject: Re: inclusions WAS: Increased company involvement