Re: [PATCH] Add enable_copy_program GUC to control COPY PROGRAM - Mailing list pgsql-hackers

From Jelte Fennema-Nio
Subject Re: [PATCH] Add enable_copy_program GUC to control COPY PROGRAM
Date
Msg-id CAGECzQRaihL5fZ94Vf+P7hw+y2u6sV_qOQfeJJDMmAh29SOkdA@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Add enable_copy_program GUC to control COPY PROGRAM  (Kirill Reshke <reshkekirill@gmail.com>)
Responses Re: [PATCH] Add enable_copy_program GUC to control COPY PROGRAM
List pgsql-hackers
On Thu, 4 Dec 2025 at 11:56, Kirill Reshke <reshkekirill@gmail.com> wrote:
>  > One idea would be to disallow FROM PROGRAM when connecting over the
> network instead of a Unix socke
>
> How this would be protected from connecting to PostgreSQL over the
> network and then executing dblink, making local (socket) connection?

Good question. I think the easiest would be to always disallow FROM
PROGRAM (by default) instead of only when connecting over the network.

Another option would be to have dblink (and pg_fdw) tell postgres (wih
e.g. a GUC being set in the StartupMessage) that it should be
considered a remote connection for these purposes.



pgsql-hackers by date:

Previous
From: Matthias van de Meent
Date:
Subject: Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements
Next
From: Andres Freund
Date:
Subject: Re: pgsql: Add pg_atomic_unlocked_write_u64