| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Neil Conway <neilc(at)samurai(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: locks in CREATE TRIGGER, ADD FK |
| Date: | 2005-03-23 01:40:21 |
| Message-ID: | 4240C905.9080301@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
If you want to be my friend forever, then fix CLUSTER so that it uses
sharerowexclusive as well :D
Chris
Neil Conway wrote:
> Neil Conway wrote:
>
>> AndrewSN pointed out on IRC that ALTER TABLE ... ADD FOREIGN KEY and
>> CREATE TRIGGER both acquire AccessExclusiveLocks on the table they are
>> adding triggers to (the PK table, in the case of ALTER TABLE). Is this
>> necessary? I don't see why we can't allow SELECT queries on the table
>> to proceed while the trigger is being added.
>
>
> Attached is a patch that changes both to use ShareRowExclusiveLock, and
> updates the documentation accordingly. I'll apply this later today,
> barring any objections.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Qingqing Zhou | 2005-03-23 01:42:35 | Re: Prevent conflicting SET options from being set |
| Previous Message | Neil Conway | 2005-03-23 01:32:58 | Re: locks in CREATE TRIGGER, ADD FK |