Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: BUG #15720: `executor could not find named tuplestore ABC` in
 AFTER DELETE trigger referencing OLD TABLE as ABC
From: Jason Madden <jason.madden@nextthought.com>
In-Reply-To: <24823.1562687102@sss.pgh.pa.us>
Date: Tue, 9 Jul 2019 10:55:38 -0500
Cc: Thomas Munro <thomas.munro@gmail.com>,
 PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <276540DF-C02E-44A4-A042-E0F245EC3129@nextthought.com>
References: <15720-38c2b29e5d720187@postgresql.org>
 <CA+hUKGJbSd1fxUXwbV2Cvf_wE4gL9vWO3B38FB+1R_j7MzQ9hA@mail.gmail.com>
 <27B30574-291E-4C33-B89F-B690FB6CA492@nextthought.com>
 <24823.1562687102@sss.pgh.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Precedence: bulk


> On Jul 9, 2019, at 10:45, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>=20
>=20
> FYI, we're now thinking that the problem here is unrelated to =
partitions
> but instead is a bug in EPQ, which is a subsystem that's entered only =
when
> a row to be locked/updated is found to have just been updated by some
> concurrent transaction.  See
>=20
> =
https://www.postgresql.org/message-id/flat/15900-bc482754fe8d7415%40postgr=
esql.org
>=20
> If you're in a position to build a custom version of Postgres, you
> might try whether the patch proposed in that thread resolves your
> problem.

Thank you for the update. Unfortunately, I no longer work with that =
system and aren't able to try to reproduce the issue.

~Jason=