Skip to content
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

Allow to run pg_repack by non-superuser #431

Merged
merged 2 commits into from
Nov 7, 2024

Commits on Oct 30, 2024

  1. Fixed segmentation fault

    Fixed the bug that segmentation fault occurs when default_transaction_read_only is turned on during repacking. bug: #426
    JennyJennyChen authored and za-arthur committed Oct 30, 2024
    Configuration menu
    Copy the full SHA
    632f67d View commit details
    Browse the repository at this point in the history

Commits on Nov 1, 2024

  1. Allow to run pg_repack by non-superuser

    Now everybody how has access to repack_trigger() and repack_apply() and
    relevant objects can call that functions.
    
    Functions repack_swap(), repack_drop() and repack_index_swap() can be
    called by superuser and owners of a table.
    
    Cherry-pick the commit 326b6e1 to not cause segmentation fault when
    using -k option and not having enough permissions.
    za-arthur committed Nov 1, 2024
    Configuration menu
    Copy the full SHA
    a692b14 View commit details
    Browse the repository at this point in the history