Skip to content

Update the changing database default tablespace #558

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.

Sign up for GitHub

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

Open
Andriciuc wants to merge 2 commits into
base: main
Choose a base branch
from
+7 −6
Open

Update the changing database default tablespace #558

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
83c933a
Update the changing database default tablespace
Andriciuc Mar 31, 2026
2275a00
Add workaround for user
Andriciuc Apr 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 7 additions & 6 deletions documentation/docs/index/tde-limitations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,16 +49,17 @@ Limitations of `pg_tde` {{release}}:

The `pg_upgrade` tool does not properly handle the internal encryption keys used by `pg_tde`, which prevents the upgraded cluster from decrypting encrypted relations.

## Changing the database default tablespace
## `ALTER DATABASE ... SET TABLESPACE`

!!! warning "Changing the database default tablespace is not supported with `pg_tde`"
Changing the default tablespace of a database is currently not supported when using `pg_tde`.
!!! warning "Changing a database tablespace has limited support with `pg_tde`"
The `ALTER DATABASE ... SET TABLESPACE` command bypasses PostgreSQL's storage manager (SMGR), which `pg_tde` relies on to enforce encryption.

This operation bypasses PostgreSQL's storage manager (SMGR), which is not supported by `pg_tde`.
- If encrypted objects exist in the database's default tablespace, the operation is refused.
- If no encrypted objects are present in the default tablespace, the operation is allowed.

As a safeguard, `pg_tde` blocks the operation if encrypted objects are detected in the default tablespace.
Only objects in the default tablespace are checked. Objects in other tablespaces are not evaluated by `pg_tde`.

Objects located outside the default tablespace are not affected by this command.
To move encrypted tables individually, use `ALTER TABLE ... SET TABLESPACE`.
Copy link
Copy Markdown
Collaborator

@jeltz jeltz Apr 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A bit weird way to phrase it. Maybe it should be more like: "A workaround is to ...".


## Currently unsupported WAL tools

Expand Down