-
Notifications
You must be signed in to change notification settings - Fork 177
Issues: reorg/pg_repack
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Recommendations to run pg_repack(1.5.0) on logical replica server
waiting for author
#436
opened Dec 19, 2024 by
Durgamahesh671
Lock issue with 1.5.1 on partitioned table repack
waiting for author
#435
opened Dec 13, 2024 by
ankitml
pg_repack failure with ERROR SET TRANSACTION ISOLATION LEVEL on AWS Aurora Postgresql 14.10
#415
opened Aug 21, 2024 by
racha2793
Error if the table is renamed concurrently during repacking
enhancement
#391
opened Apr 11, 2024 by
JohnHien
All target table reads & writes blocked because of autovacuum on repack temporary table
#371
opened Nov 9, 2023 by
schmave
Overriding
idle_in_transaction_session_timeout
doesn't seem to work properly
enhancement
#366
opened Oct 16, 2023 by
franciscoreinolds
pg_repack use SeqScan for read table. Can we use Parallel Seq Scan like the Command Copy does?
enhancement
#365
opened Oct 11, 2023 by
VladMak
simple_prompt() hangs because SIGINT handler was overridden
bug
#356
opened Jun 7, 2023 by
za-arthur
Conflicting transaction is not terminated if it is open during pg_repack execution
needs more work
#311
opened May 24, 2022 by
markosutic
pg_repack is not terminating conflicting queries when repacking only indexes
#310
opened May 24, 2022 by
markosutic
Question: Why does pg_repack change the current tablespace to pg_default, by default?
#305
opened Mar 18, 2022 by
mridude23
How to know pg_repack succeeded or failed in both table mode and index mode
waiting for author
#302
opened Feb 14, 2022 by
yinan8128
Previous Next
ProTip!
Exclude everything labeled
bug
with -label:bug.