-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation fault #426
Comments
Why would you do that? |
JennyJennyChen
added a commit
to JennyJennyChen/pg_repack
that referenced
this issue
Oct 16, 2024
Fixed the bug that segmentation fault occurs when default_transaction_read_only is turned on during repacking. bug: reorg#426
This was referenced Oct 16, 2024
Because when the disk capacity is insufficient, the automatic protection is triggered, all write transactions are interrupted and write transactions are eliminated. Anyway, no matter under any circumstances and any settings, coredump should not occur. |
za-arthur
pushed a commit
that referenced
this issue
Oct 30, 2024
Fixed the bug that segmentation fault occurs when default_transaction_read_only is turned on during repacking. bug: #426
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
session A:
pgbench -i -s 1000 pgbenchdb
pg_repack -d pgbenchdb -t pgbench_accounts -k
Start session B connect DB during the repack process
session B:
alter system set default_transaction_read_only=on;
SELECT pg_reload_conf();
session A repack enters an infinite loop, error stack burst, coredump
The text was updated successfully, but these errors were encountered: