Re: Required locks for ANALYZE
Tom Lane <[email protected]>
| Newsgroups | gmane.comp.db.postgresql.devel.documentation |
|---|---|
| Message-ID | <[email protected]> |
PG Doc comments form <[email protected]> writes: > Therefore, in my opinion, the below paragraph should be amended as below. > * Before > ----- > ANALYZE requires only a read lock on the target table, so it can run in > parallel with other activity on the table. > ----- > * After > ----- > ANALYZE requires only a SHARE UPDATE EXCLUSIVE lock on the target table, so > it can run in parallel with queries requiring ACCESS SHARE/ROW SHARE/ROW > EXCLUSIVE locks such as SELECT, UPDATE, DELETE, INSERT on the table. > ----- This does not really seem like an improvement. The second formulation is pedantically correct, but also unintelligible. Maybe we could make it say "run in parallel with non-DDL activity" ? regards, tom lane