Re: Change lock requirements for adding a trigger
От | Decibel! |
---|---|
Тема | Re: Change lock requirements for adding a trigger |
Дата | |
Msg-id | F38A0C4E-C087-4F42-B5AA-9C7A6E9026B0@decibel.org обсуждение исходный текст |
Ответ на | Re: Change lock requirements for adding a trigger (Simon Riggs <simon@2ndquadrant.com>) |
Ответы |
Re: Change lock requirements for adding a trigger
|
Список | pgsql-hackers |
On May 30, 2008, at 9:51 AM, Simon Riggs wrote: > On Thu, 2008-05-29 at 19:18 -0500, Decibel! wrote: >> Is there a reason that we can't add a trigger to a table while a >> select is running? This is a serious pain when trying to setup >> londiste or slony. > > This is constrained by locking. > > There are a subset of DDL commands that might be able to be performed > with just an ExclusiveLock or ShareLock rather than an > AccessExclusiveLock. Nobody has studied which sub-statements this > might > apply to, but its do-able since CREATE INDEX already does this. Is there a good way to determine this other than depending on knowledge of the source code? -- Decibel!, aka Jim C. Nasby, Database Architect decibel@decibel.org Give your computer some brain candy! www.distributed.net Team #1828
В списке pgsql-hackers по дате отправления: