| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Andreas Karlsson <andreas(at)proxel(dot)se> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PATCH: Reducing lock strength of trigger and foreign key DDL |
| Date: | 2015-02-13 01:10:44 |
| Message-ID: | CAB7nPqTt3V9fG3F+9yYa8b-H9ya6z6E4zEuOkahesVhGM2CvKw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Feb 8, 2015 at 10:05 AM, Andreas Karlsson <andreas(at)proxel(dot)se> wrote:
> On 01/30/2015 07:48 AM, Michael Paquier wrote:
>>
>> Looking at the latest patch, it seems that in
>> AlterTableGetLockLevel(at)tablecmds(dot)c we ought to put AT_ReAddConstraint,
>> AT_AddConstraintRecurse and AT_ProcessedConstraint under the same
>> banner as AT_AddConstraint. Thoughts?
>
>
> A new version of the patch is attached which treats them as the same for
> locking. I think it is correct and improves readability to do so.
Well then, let's switch it to "Ready for committer". I am moving as
well this entry to the next CF with the same status.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Naoya Anzai | 2015-02-13 01:16:44 | Re: Table-level log_autovacuum_min_duration |
| Previous Message | Michael Paquier | 2015-02-13 01:06:40 | Re: Commit fest 2015-12 enters money time |