Re: BUG #18559: Crash after detaching a partition concurrently from another session - Mailing list pgsql-bugs
From | Alvaro Herrera from 2ndQuadrant |
---|---|
Subject | Re: BUG #18559: Crash after detaching a partition concurrently from another session |
Date | |
Msg-id | 202408122233.bo4adt3vh5bi@alvherre.pgsql Whole thread Raw |
In response to | Re: BUG #18559: Crash after detaching a partition concurrently from another session (Alvaro Herrera from 2ndQuadrant <alvherre@alvh.no-ip.org>) |
Responses |
Re: BUG #18559: Crash after detaching a partition concurrently from another session
|
List | pgsql-bugs |
On 2024-Aug-12, Alvaro Herrera from 2ndQuadrant wrote: > On 2024-Aug-10, Junwang Zhao wrote: > > > > IIUC, a simple fix would be to retry if an entry is not found. Attached a patch. > > > > I can reproduce the issue, and the patch LGTM. > > Interesting issue, thanks for reporting and putting together a > reproducer. I have added some comments to the proposed patch, so here's > a v2 for it. I'm going to write a commit message for it and push to all > branches since 14. Dept. of second thoughts. I couldn't find any reason why it's okay to dereference the return value from systable_getnext() without verifying that it's not NULL, so I added the check to the older branches too. As far as I know we've never had a crash report that could be traced to lack of that check, but that code still looks like it's assuming a little too much. One more thing here. Applying the test scripts that I used for the previous bug with addition of DROP after the DETACH CONCURRENTLY, I get a different failure during planning, which reports this error: ERROR: could not open relation with OID 457639 STATEMENT: select * from p where a = $1; and changing that error (in relation_open) from ERROR to PANIC would result in this backtrace: #0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 #1 0x00007f149c3cae8f in __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78 #2 0x00007f149c37bfb2 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x00007f149c366472 in __GI_abort () at ./stdlib/abort.c:79 #4 0x0000557db57b8611 in errfinish (filename=<optimized out>, lineno=61, funcname=0x557db5816128 <__func__.1> "relation_open") at ../../../../../../pgsql/source/master/src/backend/utils/error/elog.c:599 #5 0x0000557db52441ad in relation_open (relationId=17466, lockmode=lockmode@entry=1) at ../../../../../../pgsql/source/master/src/backend/access/common/relation.c:61 #6 0x0000557db537d1d9 in table_open (relationId=<optimized out>, lockmode=lockmode@entry=1) at ../../../../../../pgsql/source/master/src/backend/access/table/table.c:44 #7 0x0000557db55b0cf8 in expand_partitioned_rtentry (root=root@entry=0x557db9c8b530, relinfo=relinfo@entry=0x557db9c8c2d8, parentrte=parentrte@entry=0x557db9c8c178, parentRTindex=parentRTindex@entry=1, parentrel=parentrel@entry=0x7f149bc46060,parent_updatedCols=0x0, top_parentrc=0x0, lockmode=1) at ../../../../../../pgsql/source/master/src/backend/optimizer/util/inherit.c:390 #8 0x0000557db55b121f in expand_inherited_rtentry (root=root@entry=0x557db9c8b530, rel=0x557db9c8c2d8, rte=0x557db9c8c178,rti=rti@entry=1) at ../../../../../../pgsql/source/master/src/backend/optimizer/util/inherit.c:154 #9 0x0000557db558e11a in add_other_rels_to_query (root=root@entry=0x557db9c8b530) at ../../../../../../pgsql/source/master/src/backend/optimizer/plan/initsplan.c:214 #10 0x0000557db5591983 in query_planner (root=root@entry=0x557db9c8b530, qp_callback=qp_callback@entry=0x557db5593470 <standard_qp_callback>, qp_extra=qp_extra@entry=0x7ffd987c39e0) at ../../../../../../pgsql/source/master/src/backend/optimizer/plan/planmain.c:268 #11 0x0000557db5597968 in grouping_planner (root=root@entry=0x557db9c8b530, tuple_fraction=<optimized out>, tuple_fraction@entry=0,setops=setops@entry=0x0) at ../../../../../../pgsql/source/master/src/backend/optimizer/plan/planner.c:1520 #12 0x0000557db559a8f3 in subquery_planner (glob=glob@entry=0x557db9c8c758, parse=parse@entry=0x557db9c8bf68, parent_root=parent_root@entry=0x0, hasRecursion=hasRecursion@entry=false, tuple_fraction=tuple_fraction@entry=0, setops=setops@entry=0x0) at ../../../../../../pgsql/source/master/src/backend/optimizer/plan/planner.c:1089 #13 0x0000557db559acea in standard_planner (parse=0x557db9c8bf68, query_string=<optimized out>, cursorOptions=2048, boundParams=0x0) at ../../../../../../pgsql/source/master/src/backend/optimizer/plan/planner.c:415 #14 0x0000557db5677117 in pg_plan_query (querytree=querytree@entry=0x557db9c8bf68, query_string=query_string@entry=0x557db9cb34c8"select * from p where a = $1;", cursorOptions=cursorOptions@entry=2048, boundParams=boundParams@entry=0x0) at ../../../../../pgsql/source/master/src/backend/tcop/postgres.c:912 #15 0x0000557db5677273 in pg_plan_queries (querytrees=querytrees@entry=0x557db9d69268, query_string=0x557db9cb34c8 "select* from p where a = $1;", cursorOptions=2048, boundParams=boundParams@entry=0x0) at ../../../../../pgsql/source/master/src/backend/tcop/postgres.c:1006 #16 0x0000557db57a39b3 in BuildCachedPlan (plansource=plansource@entry=0x557db9c5ff10, qlist=qlist@entry=0x557db9d69268,boundParams=boundParams@entry=0x0, queryEnv=queryEnv@entry=0x0) at ../../../../../../pgsql/source/master/src/backend/utils/cache/plancache.c:962 #17 0x0000557db57a4204 in GetCachedPlan (plansource=plansource@entry=0x557db9c5ff10, boundParams=boundParams@entry=0x557db9cc0778,owner=owner@entry=0x0, queryEnv=queryEnv@entry=0x0) at ../../../../../../pgsql/source/master/src/backend/utils/cache/plancache.c:1199 #18 0x0000557db56786c5 in exec_bind_message (input_message=0x7ffd987c3e70) at ../../../../../pgsql/source/master/src/backend/tcop/postgres.c:2017 #19 PostgresMain (dbname=<optimized out>, username=<optimized out>) at ../../../../../pgsql/source/master/src/backend/tcop/postgres.c:4814 Clearly this is undesirable, but I'm not sure how strongly we need to pursue a fix for it. It seems hard to forbid dropping the table after the detach. Is it enough to advise users to not drop partitions immediately after detaching them? Is this a sign of a more fundamental problem in the mechanism for DETACH CONCURRENTLY when used together with prepared statements? -- Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/ "Industry suffers from the managerial dogma that for the sake of stability and continuity, the company should be independent of the competence of individual employees." (E. Dijkstra)
pgsql-bugs by date: