Re: ALTER TABLE SET STATISTICS requires AccessExclusiveLock
От | Alvaro Herrera |
---|---|
Тема | Re: ALTER TABLE SET STATISTICS requires AccessExclusiveLock |
Дата | |
Msg-id | 20090807195848.GC5290@alvh.no-ip.org обсуждение исходный текст |
Ответ на | Re: ALTER TABLE SET STATISTICS requires AccessExclusiveLock (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: ALTER TABLE SET STATISTICS requires
AccessExclusiveLock
|
Список | pgsql-hackers |
Tom Lane wrote: > Peter Eisentraut <peter_e@gmx.net> writes: > > Is there a good reason for $subject, other than that the code is entangled > > with other ALTER TABLE code? > > I think it could be lower, but it would take nontrivial restructuring of > the ALTER TABLE support. In particular, consider what happens when you > have a list of subcommands that don't all require the same lock level. > I think you'd need to scan the list and find the highest required lock > level before starting ... IIRC there was a patch from Simon to address this issue, but it had some holes which he didn't have time to close, so it sank. Maybe this can be resurrected and fixed. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.
В списке pgsql-hackers по дате отправления: