Re: PATCH: Reducing lock strength of trigger and foreign key DDL
От | Michael Paquier |
---|---|
Тема | Re: PATCH: Reducing lock strength of trigger and foreign key DDL |
Дата | |
Msg-id | CAB7nPqRRX_fSK5r7DXXfTFGPSZoV+9kgF3ZO8vq1n4-FnWz09Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: PATCH: Reducing lock strength of trigger and foreign key DDL (Andreas Karlsson <andreas@proxel.se>) |
Ответы |
Re: PATCH: Reducing lock strength of trigger and foreign
key DDL
Re: PATCH: Reducing lock strength of trigger and foreign key DDL |
Список | pgsql-hackers |
On Fri, Jan 23, 2015 at 8:55 AM, Andreas Karlsson <andreas@proxel.se> wrote: > On 01/22/2015 10:31 PM, Andreas Karlsson wrote: >> >> I agree with this view, and am not sure myself that it is worth lowering >> the lock level of ALTER TRIGGER RENAME. I have attached a patch without >> the changes to ALTER TRIGGER and ruleutils.c and also fixes the comment >> issues noted by Andres. > > > Whops, forgot to include the isolation tests. Ok, so the deal is to finally reduce the locks to ShareRowExclusiveLock for the following commands : - CREATE TRIGGER - ALTER TABLE ENABLE/DISABLE - ALTER TABLE ADD CONSTRAINT Looking at the latest patch, it seems that in AlterTableGetLockLevel@tablecmds.c we ought to put AT_ReAddConstraint, AT_AddConstraintRecurse and AT_ProcessedConstraint under the same banner as AT_AddConstraint. Thoughts? -- Michael
В списке pgsql-hackers по дате отправления: