Re: a modest improvement to get_object_address()
От
Tom Lane
Тема
Re: a modest improvement to get_object_address()
Дата
Msg-id
13761.1320852790@sss.pgh.pa.us
Ответ на
Re: a modest improvement to get_object_address() (Robert Haas)
Список
Дерево обсуждения
a modest improvement to get_object_address() Robert Haas <robertmhaas@gmail.com>
Re: a modest improvement to get_object_address() Tom Lane <tgl@sss.pgh.pa.us>
Re: a modest improvement to get_object_address() Robert Haas <robertmhaas@gmail.com>
Re: a modest improvement to get_object_address() Tom Lane <tgl@sss.pgh.pa.us>
Re: a modest improvement to get_object_address() Robert Haas <robertmhaas@gmail.com>
Re: a modest improvement to get_object_address() Cédric Villemain <cedric.villemain.debian@gmail.com>
Re: a modest improvement to get_object_address() Robert Haas <robertmhaas@gmail.com>
Re: a modest improvement to get_object_address() Cédric Villemain <cedric.villemain.debian@gmail.com>
Re: a modest improvement to get_object_address() Robert Haas <robertmhaas@gmail.com>
Re: a modest improvement to get_object_address() Dimitri Fontaine <dimitri@2ndQuadrant.fr>
Re: a modest improvement to get_object_address() Robert Haas <robertmhaas@gmail.com>
Robert Haas writes: > On Wed, Nov 9, 2011 at 9:54 AM, Tom Lane 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. regards, tom lane
В списке pgsql-hackers по дате отправления