Re: Avoid orphaned objects dependencies, take 3
От | Robert Haas |
---|---|
Тема | Re: Avoid orphaned objects dependencies, take 3 |
Дата | |
Msg-id | CA+Tgmob_6FpJGkBRMOg+VrJ=eMHEyAC8-7HJvjMDShQd5Tt3Fw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Avoid orphaned objects dependencies, take 3 (Bertrand Drouvot <bertranddrouvot.pg@gmail.com>) |
Ответы |
Re: Avoid orphaned objects dependencies, take 3
|
Список | pgsql-hackers |
On Fri, Jun 7, 2024 at 4:41 AM Bertrand Drouvot <bertranddrouvot.pg@gmail.com> wrote: > Do you still find the code hard to maintain with v9? I don't think it substantially changes my concerns as compared with the earlier version. > > but we're not similarly careful about other operations e.g. > > ConstraintSetParentConstraint is called by DefineIndex which calls > > table_open(childRelId, ...) first, but there's no logic in DefineIndex > > to lock the constraint. > > table_open(childRelId, ...) would lock any "ALTER TABLE <childRelId> DROP CONSTRAINT" > already. Not sure I understand your concern here. I believe this is not true. This would take a lock on the table, not the constraint itself. -- Robert Haas EDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: