Skip to content

Commit 96105eb

Browse files
committed
Fix partition pruning setup during DETACH CONCURRENTLY
When detaching partition in concurrent mode, it's possible for partition descriptors to not match the set that was recently seen when the plan was made, causing an assertion failure or (in production builds) failure to construct a working plan. The case that was reported involves prepared statements, but I think it may be possible to hit this bug without that too. The problem is that CreatePartitionPruneState is constructing a PartitionPruneState under the assumption that new partitions can be added, but never removed, but it turns out that this isn't true: a prepared statement gets replanned when the DETACH CONCURRENTLY session sends out its invalidation message, but if the invalidation message arrives after ExecInitAppend started, we would build a partition descriptor without the partition, and then CreatePartitionPruneState would refuse to work with it. CreatePartitionPruneState already contains code to deal with the new descriptor having more partitions than before (and behaving for the extra partitions as if they had been pruned), but doesn't have code to deal with less partitions than before, and it is naïve about the case where the number of partitions is the same. We could simply add that a new stanza for less partitions than before, and in simple testing it works to do that; but it's possible to press the test scripts even further and hit the case where one partition is added and a partition is removed quickly enough that we see the same number of partitions, but they don't actually match, causing hangs during execution. To cope with both these problems, we now memcmp() the arrays of partition OIDs, and do a more elaborate mapping (relying on the fact that both OID arrays are in partition-bounds order) if they're not identical. Backpatch to 14, where DETACH CONCURRENTLY appeared. Reported-by: yajun Hu <[email protected]> Reviewed-by: Tender Wang <[email protected]> Discussion: https://postgr.es/m/[email protected]
1 parent 3c469a9 commit 96105eb

File tree

1 file changed

+60
-50
lines changed

1 file changed

+60
-50
lines changed

src/backend/executor/execPartition.c

Lines changed: 60 additions & 50 deletions
Original file line numberDiff line numberDiff line change
@@ -1934,67 +1934,58 @@ CreatePartitionPruneState(PlanState *planstate, PartitionPruneInfo *pruneinfo)
19341934
/*
19351935
* Initialize the subplan_map and subpart_map.
19361936
*
1937-
* Because we request detached partitions to be included, and
1938-
* detaching waits for old transactions, it is safe to assume that
1939-
* no partitions have disappeared since this query was planned.
1937+
* The set of partitions that exist now might not be the same that
1938+
* existed when the plan was made. The normal case is that it is;
1939+
* optimize for that case with a quick comparison, and just copy
1940+
* the subplan_map and make subpart_map point to the one in
1941+
* PruneInfo.
19401942
*
1941-
* However, new partitions may have been added.
1943+
* For the case where they aren't identical, we could have more
1944+
* partitions on either side; or even exactly the same number of
1945+
* them on both but the set of OIDs doesn't match fully. Handle
1946+
* this by creating new subplan_map and subpart_map arrays that
1947+
* corresponds to the ones in the PruneInfo where the new
1948+
* partition descriptor's OIDs match. Any that don't match can be
1949+
* set to -1, as if they were pruned. Both arrays must be in
1950+
* numerical OID order.
19421951
*/
1943-
Assert(partdesc->nparts >= pinfo->nparts);
19441952
pprune->nparts = partdesc->nparts;
19451953
pprune->subplan_map = palloc(sizeof(int) * partdesc->nparts);
1946-
if (partdesc->nparts == pinfo->nparts)
1954+
1955+
if (partdesc->nparts == pinfo->nparts &&
1956+
memcmp(partdesc->oids, pinfo->relid_map,
1957+
sizeof(int) * partdesc->nparts) == 0)
19471958
{
1948-
/*
1949-
* There are no new partitions, so this is simple. We can
1950-
* simply point to the subpart_map from the plan, but we must
1951-
* copy the subplan_map since we may change it later.
1952-
*/
19531959
pprune->subpart_map = pinfo->subpart_map;
19541960
memcpy(pprune->subplan_map, pinfo->subplan_map,
19551961
sizeof(int) * pinfo->nparts);
1956-
1957-
/*
1958-
* Double-check that the list of unpruned relations has not
1959-
* changed. (Pruned partitions are not in relid_map[].)
1960-
*/
1961-
#ifdef USE_ASSERT_CHECKING
1962-
for (int k = 0; k < pinfo->nparts; k++)
1963-
{
1964-
Assert(partdesc->oids[k] == pinfo->relid_map[k] ||
1965-
pinfo->subplan_map[k] == -1);
1966-
}
1967-
#endif
19681962
}
19691963
else
19701964
{
19711965
int pd_idx = 0;
19721966
int pp_idx;
19731967

19741968
/*
1975-
* Some new partitions have appeared since plan time, and
1976-
* those are reflected in our PartitionDesc but were not
1977-
* present in the one used to construct subplan_map and
1978-
* subpart_map. So we must construct new and longer arrays
1979-
* where the partitions that were originally present map to
1980-
* the same sub-structures, and any added partitions map to
1981-
* -1, as if the new partitions had been pruned.
1969+
* When the partition arrays are not identical, there could be
1970+
* some new ones but it's also possible that one was removed;
1971+
* we cope with both situations by walking the arrays and
1972+
* discarding those that don't match.
19821973
*
1983-
* Note: pinfo->relid_map[] may contain InvalidOid entries for
1984-
* partitions pruned by the planner. We cannot tell exactly
1985-
* which of the partdesc entries these correspond to, but we
1986-
* don't have to; just skip over them. The non-pruned
1987-
* relid_map entries, however, had better be a subset of the
1988-
* partdesc entries and in the same order.
1974+
* If the number of partitions on both sides match, it's still
1975+
* possible that one partition has been detached and another
1976+
* attached. Cope with that by creating a map that skips any
1977+
* mismatches.
19891978
*/
19901979
pprune->subpart_map = palloc(sizeof(int) * partdesc->nparts);
1980+
19911981
for (pp_idx = 0; pp_idx < partdesc->nparts; pp_idx++)
19921982
{
19931983
/* Skip any InvalidOid relid_map entries */
19941984
while (pd_idx < pinfo->nparts &&
19951985
!OidIsValid(pinfo->relid_map[pd_idx]))
19961986
pd_idx++;
19971987

1988+
recheck:
19981989
if (pd_idx < pinfo->nparts &&
19991990
pinfo->relid_map[pd_idx] == partdesc->oids[pp_idx])
20001991
{
@@ -2004,24 +1995,43 @@ CreatePartitionPruneState(PlanState *planstate, PartitionPruneInfo *pruneinfo)
20041995
pprune->subpart_map[pp_idx] =
20051996
pinfo->subpart_map[pd_idx];
20061997
pd_idx++;
1998+
continue;
20071999
}
2008-
else
2000+
2001+
/*
2002+
* There isn't an exact match in the corresponding
2003+
* positions of both arrays. Peek ahead in
2004+
* pinfo->relid_map to see if we have a match for the
2005+
* current partition in partdesc. Normally if a match
2006+
* exists it's just one element ahead, and it means the
2007+
* planner saw one extra partition that we no longer see
2008+
* now (its concurrent detach finished just in between);
2009+
* so we skip that one by updating pd_idx to the new
2010+
* location and jumping above. We can then continue to
2011+
* match the rest of the elements after skipping the OID
2012+
* with no match; no future matches are tried for the
2013+
* element that was skipped, because we know the arrays to
2014+
* be in the same order.
2015+
*
2016+
* If we don't see a match anywhere in the rest of the
2017+
* pinfo->relid_map array, that means we see an element
2018+
* now that the planner didn't see, so mark that one as
2019+
* pruned and move on.
2020+
*/
2021+
for (int pd_idx2 = pd_idx + 1; pd_idx2 < pinfo->nparts; pd_idx2++)
20092022
{
2010-
/* this partdesc entry is not in the plan */
2011-
pprune->subplan_map[pp_idx] = -1;
2012-
pprune->subpart_map[pp_idx] = -1;
2023+
if (pd_idx2 >= pinfo->nparts)
2024+
break;
2025+
if (pinfo->relid_map[pd_idx2] == partdesc->oids[pp_idx])
2026+
{
2027+
pd_idx = pd_idx2;
2028+
goto recheck;
2029+
}
20132030
}
2014-
}
20152031

2016-
/*
2017-
* It might seem that we need to skip any trailing InvalidOid
2018-
* entries in pinfo->relid_map before checking that we scanned
2019-
* all of the relid_map. But we will have skipped them above,
2020-
* because they must correspond to some partdesc->oids
2021-
* entries; we just couldn't tell which.
2022-
*/
2023-
if (pd_idx != pinfo->nparts)
2024-
elog(ERROR, "could not match partition child tables to plan elements");
2032+
pprune->subpart_map[pp_idx] = -1;
2033+
pprune->subplan_map[pp_idx] = -1;
2034+
}
20252035
}
20262036

20272037
/* present_parts is also subject to later modification */

0 commit comments

Comments
 (0)