Unverified Commit d3f2fbb4 authored by Dimitri Fontaine's avatar Dimitri Fontaine Committed by GitHub
Browse files

Fix when we VACUUM ANALYZE. (#228)

Careful reading of the Explicit Locking chapter of Postgres documentation
shows that VACUUM and ANALYZE take a SHARE UPDATE EXCLUSIVE lock against the
target table, and CREATE INDEX take a SHARE lock, which conflicts with the
former one.

  https://www.postgresql.org/docs/current/explicit-locking.html

So we can't actually VACUUM ANALYZE a table while building the indexes and
then constraints on top of that. The queueing of the VACUUM operations is
now done after the indexes and constraints are built.
parent 39bf9825
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment