mirror of https://github.com/citusdata/citus.git
43a540cff1
pg_dist_node and pg_dist_colocation have a primary key index, not a replica identity index. Citus catalog tables are created in public schema, which has replica identity index by default as primary key index. Later the citus catalog tables are moved to pg_catalog schema. During pg_upgrade, all tables are recreated, and given that pg_dist_colocation is found in pg_catalog schema, it is recreated in that schema, and when it is recreated it doesn't have a replica identity index, because catalog tables have no replica identity. Further action: Do we even need to acquire this lock on the primary key index? Postgres doesn't acquire such locks on indexes before deleting catalog tuples. Also, catalog tuples don't have replica identities by definition. |
||
|---|---|---|
| .. | ||
| commands | ||
| connection | ||
| deparser | ||
| executor | ||
| metadata | ||
| operations | ||
| planner | ||
| progress | ||
| relay | ||
| sql | ||
| test | ||
| transaction | ||
| utils | ||
| worker | ||
| .gitignore | ||
| Makefile | ||
| citus.control | ||
| safeclib | ||
| shared_library_init.c | ||