| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | simon(at)2ndquadrant(dot)com, drkp(at)csail(dot)mit(dot)edu, pgsql-hackers(at)postgresql(dot)org, tgl(at)sss(dot)pgh(dot)pa(dot)us |
| Subject: | Re: SIREAD lock versus ACCESS EXCLUSIVE lock |
| Date: | 2011-06-08 11:26:16 |
| Message-ID: | 4DEF5C58.2020100@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 08.06.2011 14:18, Heikki Linnakangas wrote:
> I just looked back
> at your old email where you listed the different DDL operations, and
> notice that we missed VACUUM FULL as well
> (http://archives.postgresql.org/message-id/4DBD7E91020000250003D0D6@gw.wicourts.gov)
> I'll look into that.
Never mind that, VACUUM FULL uses cluster_rel(), so that's covered already.
> ALTER INDEX was also still an open question in that email.
None of the variants of ALTER INDEX do anything that affects predicate
locks, so that's OK too.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2011-06-08 11:30:20 | Re: SIREAD lock versus ACCESS EXCLUSIVE lock |
| Previous Message | Heikki Linnakangas | 2011-06-08 11:18:33 | Re: SIREAD lock versus ACCESS EXCLUSIVE lock |