| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: funny lock mode in DropTrigger |
| Date: | 2011-10-21 16:20:57 |
| Message-ID: | 12354.1319214057@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Ah, I also noticed that the ALTER EXTENSION and SECURITY LABEL commands
> use ShareUpdateExclusiveLock, and they failed when committed to note
> this in the 13.3 chapter of the docs. Not sure how strict we are about
> documenting these things. (I note COMMENT already fails to document its
> ShareUpdExcl lock).
To my mind, the list in 13.3 is only meant to cover what lock levels are
used *with tables*. Locks applied to other kinds of objects would
probably need a different list altogether.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2011-10-21 16:37:30 | Re: Synchronized snapshots versus multiple databases |
| Previous Message | Tom Lane | 2011-10-21 16:19:35 | Re: funny lock mode in DropTrigger |