| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Lock levels for ALTER TABLE |
| Date: | 2013-01-10 04:56:14 |
| Message-ID: | 23560.1357793774@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Wed, Jan 9, 2013 at 10:27:54PM -0500, Tom Lane wrote:
>> Bruce Momjian <bruce(at)momjian(dot)us> writes:
>>> EnterpriseDB reports that our documentation states that ALTER TABLE
>>> takes SHARE UPDATE EXCLUSIVE and ACCESS EXCLUSIVE lock modes.
>> Where do they see that? We certainly reverted all of the documentation
>> that Simon changed in the original commit for that failed feature.
>> Something might have slipped through the cracks though.
> In mvcc.sgml, I see:
> --> some forms of <command>ALTER TABLE</command>.
A bit of "git blame" later, the culprit is commit
7212c77d0cabcc468fec0b9cd7f2413b64b77050, which I apparently didn't
recognize as part of what needed to be reverted in
a195e3c34f1eeb6a607c342121edf48e49067ea9. Will fix.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-01-10 05:14:46 | Re: Lock levels for ALTER TABLE |
| Previous Message | Tom Lane | 2013-01-10 04:02:58 | Re: Index build temp files |