From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Amit Langote <amitlangote09@gmail.com>
Cc: Justin Pryzby <pryzby@telsasoft.com>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: FailedAssertion("pd_idx == pinfo->nparts", File: "execPartition.c", Line: 1689)
Date: Wed, 05 Aug 2020 16:19:08 -0400
Message-ID: <2579006.1596658748@sss.pgh.pa.us> (raw)
In-Reply-To: <CA+Tgmob=XeebtddujUfHu7-UP_fbNNWGzxU1U=5wWk1ZQmJS3w@mail.gmail.com>
References: <20200802181131.GA27754@telsasoft.com>
<CA+TgmoawZkbuvP5BDBNNVp18F4tuwaZtqKUFxtH61QX7CiAV=Q@mail.gmail.com>
<20200803161133.GA21372@telsasoft.com>
<CA+HiwqETTgTh5SG9bcAdYRahEeTgpPHy+Xi=b93icoTX7j2EFg@mail.gmail.com>
<2528807.1596648630@sss.pgh.pa.us>
<CA+TgmoYMqqqHaOpfMYs8R6VJekykfRABCD=o4ovN2eUz-efYMA@mail.gmail.com>
<2550497.1596651719@sss.pgh.pa.us>
<CA+Tgmob=XeebtddujUfHu7-UP_fbNNWGzxU1U=5wWk1ZQmJS3w@mail.gmail.com>
Robert Haas <robertmhaas@gmail.com> writes:
> On Wed, Aug 5, 2020 at 2:22 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> In the longer term, it's annoying that we have no test methodology
>> for this other than "manually set a breakpoint here". If we're going
>> to allow plan-relevant DDL changes to happen with less than full table
>> lock, I think we need to improve that. I spent a little bit of time
>> just now trying to build an isolationtester case for this, and failed
>> completely. So I wonder if we can create some sort of test module that
>> allows capture of a plan tree and then execution of that plan tree later
>> (even after relcache inval would normally have forced replanning).
>> Obviously that could not be a normal SQL-accessible feature, because
>> some types of invals would make the plan completely wrong, but for
>> testing purposes it'd be mighty helpful to check that a stale plan
>> still works.
> That's an interesting idea. I don't know exactly how it would work,
> but I agree that it would allow useful testing that we can't do today.
After thinking about it for a little bit, I'm envisioning a test module
that can be loaded into a session, and then it gets into the planner_hook,
and what it does is after each planner execution, take and release an
advisory lock with some selectable ID. Then we can construct
isolationtester specs that do something like
session 1 session 2
LOAD test-module;
SET custom_guc_for_lock_id = n;
prepare test tables;
SELECT pg_advisory_lock(n);
SELECT victim-query-here;
... after planning, query blocks on lock
perform DDL changes;
SELECT pg_advisory_unlock(n);
... query executes with now-stale plan
regards, tom lane
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, robertmhaas@gmail.com, amitlangote09@gmail.com, pryzby@telsasoft.com
Subject: Re: FailedAssertion("pd_idx == pinfo->nparts", File: "execPartition.c", Line: 1689)
In-Reply-To: <2579006.1596658748@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