Failed assertion root->hasLateralRTEs on initsplan.c

Поиск
Список
Период
Сортировка
От Emre Hasegeli
Тема Failed assertion root->hasLateralRTEs on initsplan.c
Дата
Msg-id CAE2gYzx8NfaRWF10i42KKxNOZFSnkBKYWTfO3DuCLBOFhspwhg@mail.gmail.com
обсуждение исходный текст
Ответы Re: Failed assertion root->hasLateralRTEs on initsplan.c  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
I get assertion failure on initsplan.c line 1325 while executing following query
on HEAD (edc43458d797a5956f4bf39af18cf62abb0077db). It works fine
without --enable-cassert.

update subscriber set properties = hstore(a) from (select firstname,
lastname from player where player.id = subscriber.id) as a;

Backtrace:

* thread #1: tid = 0x2e16ec, 0x00007fff85f0b866
libsystem_kernel.dylib`__pthread_kill + 10, queue =
'com.apple.main-thread, stop reason = signal SIGABRT   frame #0: 0x00007fff85f0b866
libsystem_kernel.dylib`__pthread_kill+ 10   frame #1: 0x00007fff8450335c libsystem_pthread.dylib`pthread_kill + 92
frame#2: 0x00007fff82ffdbba libsystem_c.dylib`abort + 125   frame #3: 0x000000010e2b7510
 
postgres`ExceptionalCondition(conditionName=<unavailable>,
errorType=<unavailable>, fileName=<unavailable>,
lineNumber=<unavailable>) + 80 at assert.c:54   frame #4: 0x000000010e155ab6
postgres`distribute_qual_to_rels(root=<unavailable>,
clause=0x00007fd5c382e208, is_deduced='\0', below_outer_join='\0',
jointype=JOIN_INNER, qualscope=0x00007fd5c3835ee8,
ojscope=<unavailable>, outerjoin_nonnullable=<unavailable>,
deduced_nullable_relids=<unavailable>,
postponed_qual_list=<unavailable>) + 1254 at initsplan.c:1325   frame #5: 0x000000010e154a66
postgres`deconstruct_recurse(root=0x00007fd5c382c248,
jtnode=0x00007fd5c382cde0, below_outer_join='\0',
qualscope=0x00007fff51c723f8, inner_join_rels=<unavailable>,
postponed_qual_list=0x00007fff51c72400) + 870 at initsplan.c:781   frame #6: 0x000000010e1548ab
postgres`deconstruct_recurse(root=0x00007fd5c382c248,
jtnode=0x00007fd5c382bfd8, below_outer_join='\0',
qualscope=0x00007fff51c72450, inner_join_rels=0x00007fff51c72448,
postponed_qual_list=0x00007fff51c72440) + 427 at initsplan.c:732   frame #7: 0x000000010e1546a1
postgres`deconstruct_jointree(root=<unavailable>) + 81 at
initsplan.c:655   frame #8: 0x000000010e156a1b
postgres`query_planner(root=0x00007fd5c382c248,
tlist=0x00007fd5c382e398, qp_callback=0x000000010e15a660,
qp_extra=0x00007fff51c725f0) + 219 at planmain.c:145   frame #9: 0x000000010e1589d8
postgres`grouping_planner(root=0x00007fd5c382c248,
tuple_fraction=<unavailable>) + 2888 at planner.c:1243   frame #10: 0x000000010e157adf
postgres`subquery_planner(glob=0x00007fd5c4007e68,
parse=0x00007fd5c4007a30, parent_root=<unavailable>,
hasRecursion=<unavailable>, tuple_fraction=0,
subroot=0x00007fff51c72900) + 3119 at planner.c:572   frame #11: 0x000000010e156cac
postgres`standard_planner(parse=0x00007fd5c4007a30,
cursorOptions=<unavailable>, boundParams=<unavailable>) + 236 at
planner.c:210   frame #12: 0x000000010e1d6356
postgres`pg_plan_query(querytree=0x00007fd5c4007a30, cursorOptions=0,
boundParams=0x0000000000000000) + 118 at postgres.c:759   frame #13: 0x000000010e1d979a postgres`PostgresMain
[inlined]
pg_plan_queries(cursorOptions=0, querytrees=<unavailable>,
boundParams=<unavailable>) + 56 at postgres.c:818   frame #14: 0x000000010e1d9762 postgres`PostgresMain [inlined]
exec_simple_query(query_string=0x00007fd5c4006038) + 21 at
postgres.c:983   frame #15: 0x000000010e1d974d
postgres`PostgresMain(argc=<unavailable>, argv=<unavailable>,
dbname=0x00007fd5c301ac30, username=<unavailable>) + 8749 at
postgres.c:4011   frame #16: 0x000000010e184c1f postgres`PostmasterMain [inlined]
BackendRun + 7551 at postmaster.c:4085   frame #17: 0x000000010e184c00 postgres`PostmasterMain [inlined]
BackendStartup at postmaster.c:3774   frame #18: 0x000000010e184c00 postgres`PostmasterMain [inlined]
ServerLoop at postmaster.c:1585   frame #19: 0x000000010e184c00
postgres`PostmasterMain(argc=<unavailable>, argv=<unavailable>) + 7520
at postmaster.c:1240   frame #20: 0x000000010e11924f postgres`main(argc=1,
argv=0x00007fd5c2c03ec0) + 783 at main.c:194   frame #21: 0x00007fff897165fd libdyld.dylib`start + 1   frame #22:
0x00007fff897165fdlibdyld.dylib`start + 1
 



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Matheus de Oliveira
Дата:
Сообщение: Re: Bug in visibility map WAL-logging
Следующее
От: Florian Pflug
Дата:
Сообщение: Re: How to reproduce serialization failure for a read only transaction.