Re: Why is lock not released?
От | Alvaro Herrera |
---|---|
Тема | Re: Why is lock not released? |
Дата | |
Msg-id | 20050819183538.GB15622@surnet.cl обсуждение исходный текст |
Ответ на | Re: Why is lock not released? (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Why is lock not released?
|
Список | pgsql-hackers |
On Fri, Aug 19, 2005 at 01:11:54PM -0400, Tom Lane wrote: > Alvaro Herrera <alvherre@alvh.no-ip.org> writes: > > I just noticed that AlterSchemaOwner (and others like AlterFunctionOwner > > -- I haven't checked anything else yet) does not release the lock on > > pg_namespace (resp. AlterFunctionOwner) after it's done changing it. Is > > there a reason for this? > > The code's a bit inconsistent about whether it releases non-exclusive > locks on system catalogs or leaves them till transaction end. I suppose > sometime we should try to make it consistent --- but as long as you're > talking about non-exclusive locks, it doesn't really matter too much. Ok, I'll change it where I find reasonable in my "drop owned by" patch. (The locks are RowExclusive). -- Alvaro Herrera (<alvherre[a]alvh.no-ip.org>) "Cuando mañana llegue pelearemos segun lo que mañana exija" (Mowgli)
В списке pgsql-hackers по дате отправления: