pg.ddx.io pgsql-hackers@postgresql.org mailing list archive help / color / mirror / Atom feed From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Yugo NAGATA <nagata@sraoss.co.jp>
Cc: Andy Fan <zhihui.fan1213@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Cc: Tatsuo Ishii <ishii@sraoss.co.jp>
Cc: Konstantin Knizhnik <k.knizhnik@postgrespro.ru>
Cc: Thomas Munro <thomas.munro@gmail.com>
Subject: Re: Implementing Incremental View Maintenance
Date: Mon, 19 Apr 2021 17:40:31 -0400
Message-ID: <345103.1618868431@sss.pgh.pa.us> (raw )
In-Reply-To: <ea935ebc-cd3f-7a8f-563c-33c9b676d363@dunslane.net >
References: <20201001140627.1f8fafe595f545e026d110c6@sraoss.co.jp >
<024ba056-6b4f-b26c-af17-297c1bbca65a@postgrespro.ru >
<20201112.205355.393498768557598337.t-ishii@sraoss.co.jp >
<89729da8-9042-7ea0-95af-e415df6da14d@postgrespro.ru >
<20201124182133.2b7d2ee8767f4bb946226ecc@sraoss.co.jp >
<5663f5f0-48af-686c-bf3c-62d279567e2a@postgrespro.ru >
<20201222215136.39a3736a948161fb490dbc75@sraoss.co.jp >
<20201222222422.f3e34e2ac2eb4a9f510676a7@sraoss.co.jp >
<20210112190308.ee9e98c24080310a487349f3@sraoss.co.jp >
<20210122165954.d6386b0e3a530a76890b8fff@sraoss.co.jp >
<20210216103155.762054c9d38727c782f0c11b@sraoss.co.jp >
<CAKU4AWoxXkPPL2qMoAn-2skEbt+9E2MrARhcf+NKwm4JFg-uHg@mail.gmail.com >
<20210219110126.7152beb4fa4fea5b1133eef3@sraoss.co.jp >
<45b2760d-7ee9-0f46-50bf-b15fd440b52f@dunslane.net >
<20210309092049.db22add3e2863c2140290a90@sraoss.co.jp >
<20210309172750.8fd722a08ed3a2423bb25ccb@sraoss.co.jp >
<20210407182537.5fdb444f6d4510a60524baab@sraoss.co.jp >
<ea935ebc-cd3f-7a8f-563c-33c9b6! 76d363@dunslane.net >
Andrew Dunstan <andrew@dunslane.net> writes:
> This patch (v22c) just crashed for me with an assertion failure on
> Fedora 31. Here's the stack trace:
> #2 0x000000000094a54a in ExceptionalCondition
> (conditionName=conditionName@entry=0xa91dae "queryDesc->sourceText !=
> NULL", errorType=errorType@entry=0x99b468 "FailedAssertion",
> fileName=fileName@entry=0xa91468
> "/home/andrew/pgl/pg_head/src/backend/executor/execMain.c",
> lineNumber=lineNumber@entry=199) at
> /home/andrew/pgl/pg_head/src/backend/utils/error/assert.c:69
That assert just got added a few days ago, so that's why the patch
seemed OK before.
regards, tom lane
view thread (223+ messages) latest in thread
Message-ID: <345103.1618868431@sss.pgh.pa.us>
Permalink: ../345103.1618868431@sss.pgh.pa.us/
Also on: postgresql.org/message-id/345103.1618868431@sss.pgh.pa.us
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, andrew@dunslane.net, nagata@sraoss.co.jp, zhihui.fan1213@gmail.com, pgsql-hackers@lists.postgresql.org, ishii@sraoss.co.jp, k.knizhnik@postgrespro.ru, thomas.munro@gmail.com
Subject: Re: Implementing Incremental View Maintenance
In-Reply-To: <345103.1618868431@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox