public inbox for [email protected]
help / color / mirror / Atom feedFrom: Nathan Bossart <[email protected]>
To: Ayush Tiwari <[email protected]>
Cc: [email protected]
Cc: [email protected]
Subject: Re: BUG #19476: Segmentation fault in contrib/spi
Date: Thu, 14 May 2026 13:16:03 -0500
Message-ID: <agYRY_Ld26BI32bK@nathan> (raw)
In-Reply-To: <CAJTYsWWWeQvL0JaLYArnunhKfX6=g3q1Mjq_ViipW6G011dfpQ@mail.gmail.com>
References: <[email protected]>
<CAJTYsWVuNPbqS2p1gEitRLBHuytqM7OMawuzVH6g4uqGw4RBsQ@mail.gmail.com>
<[email protected]>
<CAJTYsWWh5qsJcLatT5HD9daTEbCnZUZoqaDPGiT=+EyHkEKJ2A@mail.gmail.com>
<agXx84rrzKWY9aAE@nathan>
<agX8Olw7JnK7o9se@nathan>
<CAJTYsWWWeQvL0JaLYArnunhKfX6=g3q1Mjq_ViipW6G011dfpQ@mail.gmail.com>
On Thu, May 14, 2026 at 10:42:07PM +0530, Ayush Tiwari wrote:
> Thanks, this version looks good to me. The compact form is fine, and I
> agree with preserving the pre-CVE behavior for this misconfigured case
> rather than turning it into an ERROR or no-op.
Committed.
> I think the cached cascade UPDATE plan issue is worth pursuing,
> I'll start a different hackers thread on that
> probably using the "don't cache cascade UPDATE plans" approach you
> suggested.
Great, thanks.
--
nathan
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: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: BUG #19476: Segmentation fault in contrib/spi
In-Reply-To: <agYRY_Ld26BI32bK@nathan>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox