On Wed, Nov 9, 2011 at 10:33 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Robert Haas <robertmh...@gmail.com> writes: >> On Wed, Nov 9, 2011 at 9:54 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: >>> I would think you need to drop the now-useless lock, and I sure hope >>> that RangeVarGetRelid does likewise. > >> It doesn't currently. The now-useless lock doesn't really hurt >> anything, aside from taking up space in the lock table. > > Well, there are corner cases where the object OID gets reused during > the lifetime of the transaction, and then the lock *does* do something > (and what it does would be bad). But taking up extra space in the > finite-size lock table is sufficient reason IMO to drop the lock. > It's not like these are performance-critical code paths.
OK. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers