Skip to content

Commit a25f21d

Browse files
committed
Fix pg_dump --clean with partitioned indexes.
We'd try to drop the partitions of a partitioned index separately, which is disallowed by the backend, leading to an error during restore. While the error is harmless, it causes problems if you try to use --single-transaction mode. Fortunately, there seems no need to do a DROP at all, since the partition will go away silently when we drop either the parent index or the partition's table. So just make the DROP conditional on not being a partition. Reported-by: jian he <jian.universality@gmail.com> Author: jian he <jian.universality@gmail.com> Reviewed-by: Pavel Stehule <pavel.stehule@gmail.com> Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us> Discussion: https://postgr.es/m/CACJufxF0QSdkjFKF4di-JGWN6CSdQYEAhGPmQJJCdkSZtd=oLg@mail.gmail.com Backpatch-through: 13
1 parent f04e0fa commit a25f21d

File tree

1 file changed

+20
-6
lines changed

1 file changed

+20
-6
lines changed

src/bin/pg_dump/pg_dump.c

Lines changed: 20 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -16558,7 +16558,17 @@ dumpIndex(Archive *fout, const IndxInfo *indxinfo)
1655816558
qindxname);
1655916559
}
1656016560

16561-
appendPQExpBuffer(delq, "DROP INDEX %s;\n", qqindxname);
16561+
/*
16562+
* If this index is a member of a partitioned index, the backend will
16563+
* not allow us to drop it separately, so don't try. It will go away
16564+
* automatically when we drop either the index's table or the
16565+
* partitioned index. (If, in a selective restore with --clean, we
16566+
* drop neither of those, then this index will not be dropped either.
16567+
* But that's fine, and even if you think it's not, the backend won't
16568+
* let us do differently.)
16569+
*/
16570+
if (indxinfo->parentidx == 0)
16571+
appendPQExpBuffer(delq, "DROP INDEX %s;\n", qqindxname);
1656216572

1656316573
if (indxinfo->dobj.dump & DUMP_COMPONENT_DEFINITION)
1656416574
ArchiveEntry(fout, indxinfo->dobj.catId, indxinfo->dobj.dumpId,
@@ -16611,11 +16621,15 @@ dumpIndexAttach(Archive *fout, const IndexAttachInfo *attachinfo)
1661116621
fmtQualifiedDumpable(attachinfo->partitionIdx));
1661216622

1661316623
/*
16614-
* There is no point in creating a drop query as the drop is done by
16615-
* index drop. (If you think to change this, see also
16616-
* _printTocEntry().) Although this object doesn't really have
16617-
* ownership as such, set the owner field anyway to ensure that the
16618-
* command is run by the correct role at restore time.
16624+
* There is no need for a dropStmt since the drop is done implicitly
16625+
* when we drop either the index's table or the partitioned index.
16626+
* Moreover, since there's no ALTER INDEX DETACH PARTITION command,
16627+
* there's no way to do it anyway. (If you think to change this,
16628+
* consider also what to do with --if-exists.)
16629+
*
16630+
* Although this object doesn't really have ownership as such, set the
16631+
* owner field anyway to ensure that the command is run by the correct
16632+
* role at restore time.
1661916633
*/
1662016634
ArchiveEntry(fout, attachinfo->dobj.catId, attachinfo->dobj.dumpId,
1662116635
ARCHIVE_OPTS(.tag = attachinfo->dobj.name,

0 commit comments

Comments
 (0)