You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am repacking a child partition of a partitioned table. It fails during swap after the indexes are created. I have not been able to successfully run a repack on 1.5.1, while on 1.5.0 it is succeeding.
{"levelname": "INFO", "message": "[repack.py] LOG: Initial worker 1 to build index: CREATE INDEX index_399285097 ON repack.table_399285089 USING gin (a, b, available_at, c)", "asctime": "2024-12-12 18:14:51,165"}
{"levelname": "INFO", "message": "[repack.py] LOG: Command finished in worker 1: CREATE UNIQUE INDEX index_399285097 ON repack.table_399285089 USING gin (a, b, available_at, c)", "asctime": "2024-12-12 18:14:51,165"}
{"levelname": "INFO", "message": "[repack.py] ERROR: query failed: ERROR: must hold access exclusive lock on table \"table_399285089\"", "asctime": "2024-12-12 18:14:51,165"}
{"levelname": "INFO", "message": "[repack.py] DETAIL: query was: SELECT repack.repack_swap($1)", "asctime": "2024-12-12 18:14:51,165"}
The text was updated successfully, but these errors were encountered:
Confirming, downgrading fixes it. Upgrading fails. This does not show up when a normal table that is not partitioned is repacked.
Postgres version 15. OS : Ubuntu 22.04
I am repacking a child partition of a partitioned table. It fails during swap after the indexes are created. I have not been able to successfully run a repack on 1.5.1, while on 1.5.0 it is succeeding.
The text was updated successfully, but these errors were encountered: