aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/tablespace.c
diff options
context:
space:
mode:
authorAlvaro Herrera <alvherre@alvh.no-ip.org>2019-04-24 15:30:37 -0400
committerAlvaro Herrera <alvherre@alvh.no-ip.org>2019-04-24 15:30:37 -0400
commit3b23552ad8bbb1384381b67f860019d14d5b680e (patch)
treefda1ae48d991a5d342362202471fed7a4d41d2d3 /src/backend/commands/tablespace.c
parent0fae846232148754468f6d57b3f98d5b83d90af7 (diff)
downloadpostgresql-3b23552ad8bbb1384381b67f860019d14d5b680e.tar.gz
postgresql-3b23552ad8bbb1384381b67f860019d14d5b680e.zip
Make pg_dump emit ATTACH PARTITION instead of PARTITION OF
Using PARTITION OF can result in column ordering being changed from the database being dumped, if the partition uses a column layout different from the parent's. It's not pg_dump's job to editorialize on table definitions, so this is not acceptable; back-patch all the way back to pg10, where partitioned tables where introduced. This change also ensures that partitions end up in the correct tablespace, if different from the parent's; this is an oversight in ca4103025dfe (in pg12 only). Partitioned indexes (in pg11) don't have this problem, because they're already created as independent indexes and attached to their parents afterwards. This change also has the advantage that the partition is restorable from the dump (as a standalone table) even if its parent table isn't restored. Author: David Rowley Reviewed-by: Álvaro Herrera Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com Discussion: https://postgr.es/m/20190423185007.GA27954@alvherre.pgsql
Diffstat (limited to 'src/backend/commands/tablespace.c')
0 files changed, 0 insertions, 0 deletions