diff options
| author | Michael Paquier <michael@paquier.xyz> | 2021-12-22 15:38:05 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2021-12-22 15:38:05 +0900 |
| commit | 8a22a40b2cfd1ea3218663153e5c6d7ebc68d2bf (patch) | |
| tree | e02f65ea5f057f873df40deb11b18ffedaaaf50c /src/backend/commands/explain.c | |
| parent | f9a8bc9f27e6c7569f30fc86b82129647068f6a0 (diff) | |
| download | postgresql-8a22a40b2cfd1ea3218663153e5c6d7ebc68d2bf.tar.gz postgresql-8a22a40b2cfd1ea3218663153e5c6d7ebc68d2bf.zip | |
Remove assertion for ALTER TABLE .. DETACH PARTITION CONCURRENTLY
One code path related to this flavor of ALTER TABLE was checking that
the relation to detach has to be a normal table or a partitioned table,
which would fail if using the command with a different relation kind.
Views, sequences and materialized views cannot be part of a partition
tree, so these would cause the command to fail anyway, but the assertion
was triggered. Foreign tables can be part of a partition tree, and
again the assertion would have failed. The simplest solution is just to
remove this assertion, so as we get the same failure as the
non-concurrent code path.
While on it, add a regression test in postgres_fdw for the concurrent
partition detach of a foreign table, as per a suggestion from Alexander
Lakhin.
Issue introduced in 71f4c8c.
Reported-by: Alexander Lakhin
Author: Michael Paquier, Alexander Lakhin
Reviewed-by: Peter Eisentraut, Kyotaro Horiguchi
Discussion: https://postgr.es/m/17339-a9e09aaf38a3457a@postgresql.org
Backpatch-through: 14
Diffstat (limited to 'src/backend/commands/explain.c')
0 files changed, 0 insertions, 0 deletions