-
Notifications
You must be signed in to change notification settings - Fork 177
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
Question: Why does pg_repack change the current tablespace to pg_default, by default? #305
Comments
Using the latest version of pg_repack, 1.4.8, on OnPrem PG v13 and v14, I am not able to reproduce your wrong results.
Please use the latest version of pg_repack. |
I'm sorry, I think I was wrong. You were not just talking about repacking a table in a user-defined tablespace, but a user-defined tablespace that is the default tablespace. This is still an ongoing issue. See #363. |
Not only this, but when repacking an index while using
Am I missing something? |
Just noticed that when running pg_repack on an on-prem server, it changes the current tablespace to pg_default.
Is this by design?
It's not an issue running the command with --tablespace=TBLSPC attached, but it seems counterintuitive, given the manual wording:
-s, --tablespace=TBLSPC move repacked tables to a new tablespace
I would expect that by default it will use the current tablespace, and only if I use it then the tablespace would change.
The text was updated successfully, but these errors were encountered: