| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: We broke the defense against accessing other sessions' temp tables |
| Date: | 2025-09-21 19:39:09 |
| Message-ID: | CAKFQuwa7dtfe_EUWRKd2m4Tq5+1dpkpJeS2-2GRLE_WbDutW4g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Sep 21, 2025 at 12:19 PM Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
wrote:
> On Sun, 21 Sept 2025 at 19:44, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > Yeah, if it were 18-only we'd need a powwow about whether to break
> > release freeze. But since it's been there since 17 and nobody
> > noticed, I'm content to wait till after 18.0 to fix it.
>
> People definitely noticed[1], but I agree that there's no reason to
> rush this fix out before the 18 release.
>
> Patch looks good, but obviously needs some tests.
>
> [1]:
> https://www.postgresql.org/message-id/flat/CAMEv5_syU0ZopE-2Wr8A8QksqrCyYT2hW06Rgw4RSPdyJO-%3Dfw%40mail.gmail.com
>
>
I'm presuming this report is also about the same underlying issue.
It too has a patch included.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David E. Wheeler | 2025-09-21 20:59:58 | Re: ABI Compliance Checker GSoC Project |
| Previous Message | Jelte Fennema-Nio | 2025-09-21 19:18:44 | Re: We broke the defense against accessing other sessions' temp tables |