| From: | Gurjeet Singh <gurjeet(at)singh(dot)im> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Hannu Krosing <hannuk(at)google(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Pang <robertpang(at)google(dot)com> |
| Subject: | Re: Hardening PostgreSQL via (optional) ban on local file system access |
| Date: | 2022-06-24 23:46:28 |
| Message-ID: | CABwTF4VJdi069fmWiQHdeXYncgiyc=KMWO5-6a5xiAQB1TCFEQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jun 24, 2022 at 4:13 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> On 2022-06-25 00:08:13 +0200, Hannu Krosing wrote:
> > 3) should this be back-patched (we can provide batches for all
> > supported PgSQL versions)
>
> Err, what?
Translation: Backpatching these changes to any stable versions will
not be acceptable (per the project versioning policy [1]), since these
changes would be considered new feature. These changes can break
installations, if released in a minor version.
[1]: https://www.postgresql.org/support/versioning/
Best regards,
Gurjeet
http://Gurje.et
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2022-06-24 23:59:35 | Re: Hardening PostgreSQL via (optional) ban on local file system access |
| Previous Message | David G. Johnston | 2022-06-24 23:29:38 | Re: Hardening PostgreSQL via (optional) ban on local file system access |