Re: [EXTERNAL] Re: Asking for OK for a nasty trick to resolve PG CVE-2025-1094 i

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
To: "Abraham, Danny" <danny_abraham(at)bmc(dot)com>
Cc: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: [EXTERNAL] Re: Asking for OK for a nasty trick to resolve PG CVE-2025-1094 i
Date: 2025-03-07 13:24:57
Message-ID: CAKAnmmJgHvPooiXZ5vzvONMWjcazg+Z4VEPrHW_NVFmUvYAX2g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-performance

CVE-2025-1094 has a narrow blast radius. If you are not directly affected,
I would focus your efforts on getting to 17. But the lack of an existing
process to smoothly upgrade minor revisions is worrying and something that
needs to get addressed as well.

Cheers,
Greg

--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Greg Sabino Mullane 2025-03-07 13:45:12 Re: Review my steps for rollback to restore point
Previous Message Bartosz Stalewski 2025-03-07 11:16:38 Vacuum related question

Browse pgsql-performance by date

  From Date Subject
Previous Message Laurenz Albe 2025-03-06 12:32:14 Re: [EXTERNAL] Re: Asking for OK for a nasty trick to resolve PG CVE-2025-1094 i