| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
| Cc: | Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] refint: Avoid reusing cascade UPDATE plans. |
| Date: | 2026-05-15 14:46:34 |
| Message-ID: | agcxyg89JAiESawi@nathan |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, May 15, 2026 at 04:42:45PM +0200, Álvaro Herrera wrote:
> On 2026-May-15, Nathan Bossart wrote:
>> Yeah, this may be the best option. I'm curious what others think.
>
> I think this bug makes it clear that this code has few enough users, and
> a sufficient number of bugs, that we should just nuke it. Do you really
> want to spend so much time trying to fix it? The module's documentation
> says
>
> (This functionality is long since superseded by the built-in foreign
> key mechanism, of course, but the module is still useful as an example.)
>
> but I question whether the usefulness value is really there.
>
> Would anyone oppose that?
Big +1 for removing it in v20. Or maybe even v19. I do think it is worth
trying to fix the more egregious bugs, though, as the code will still be
supported for a few years.
--
nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2026-05-15 14:59:15 | pg_recvlogical: honor source cluster file permissions for output files |
| Previous Message | Álvaro Herrera | 2026-05-15 14:42:45 | Re: [PATCH] refint: Avoid reusing cascade UPDATE plans. |