postgres.git / summary / log / commit / refs

commit    5236dcdb62ac9da00a993e0971fac4ba5e240070
Author:   Alvaro Herrera <alvherre@alvh.no-ip.org>
Date:     Mon Aug 12 22:17:56 2024 +0000
First released in: 18.0, 12.21, 13.17, 14.14, 15.9, 16.5, 17.0

    Fix creation of partition descriptor during concurrent detach+drop
    
    If a partition undergoes DETACH CONCURRENTLY immediately followed by
    DROP, this could cause a problem for a concurrent transaction
    recomputing the partition descriptor when running a prepared statement,
    because it tries to dereference a pointer to a tuple that's not found in
    a catalog scan.
    
    The existing retry logic added in commit dbca3469ebf8 is sufficient to
    cope with the overall problem, provided we don't try to dereference a
    non-existant heap tuple.
    
    Arguably, the code in RelationBuildPartitionDesc() has been wrong all
    along, since no check was added in commit 898e5e3290a7 against receiving
    a NULL tuple from the catalog scan; that bug has only become
    user-visible with DETACH CONCURRENTLY which was added in branch 14.
    Therefore, even though there's no known mechanism to cause a crash
    because of this, backpatch the addition of such a check to all supported
    branches.  In branches prior to 14, this would cause the code to fail
    with a "missing relpartbound for relation XYZ" error instead of
    crashing; that's okay, because there are no reports of such behavior
    anyway.
    
    Author: Kuntal Ghosh <kuntalghosh.2007@gmail.com>
    Reviewed-by: Junwang Zhao <zhjwpku@gmail.com>
    Reviewed-by: Tender Wang <tndrwang@gmail.com>
    Discussion: https://postgr.es/m/18559-b48286d2eacd9a4e@postgresql.org


src/backend/partitioning/partdesc.c | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/src/backend/partitioning/partdesc.c b/src/backend/partitioning/partdesc.c index 0f124a52540..c7e041933d6 100644 --- a/src/backend/partitioning/partdesc.c +++ b/src/backend/partitioning/partdesc.c @@ -164,8 +164,6 @@ RelationBuildPartitionDesc(Relation rel) Relation pg_class; SysScanDesc scan; ScanKeyData key[1]; - Datum datum; - bool isnull; pg_class = table_open(RelationRelationId, AccessShareLock); ScanKeyInit(&key[0], @@ -175,10 +173,16 @@ RelationBuildPartitionDesc(Relation rel) scan = systable_beginscan(pg_class, ClassOidIndexId, true, NULL, 1, key); tuple = systable_getnext(scan); - datum = heap_getattr(tuple, Anum_pg_class_relpartbound, - RelationGetDescr(pg_class), &isnull); - if (!isnull) - boundspec = stringToNode(TextDatumGetCString(datum)); + if (HeapTupleIsValid(tuple)) + { + Datum datum; + bool isnull; + + datum = heap_getattr(tuple, Anum_pg_class_relpartbound, + RelationGetDescr(pg_class), &isnull); + if (!isnull) + boundspec = stringToNode(TextDatumGetCString(datum)); + } systable_endscan(scan); table_close(pg_class, AccessShareLock); } [parent: 016f443648d2]