Re: [PATCH] Add enable_copy_program GUC to control COPY PROGRAM

Jelte Fennema-Nio <postgres@jeltef.nl>

From: Jelte Fennema-Nio <postgres@jeltef.nl>

To: Kirill Reshke <reshkekirill@gmail.com>

Cc: Tom Lane <tgl@sss.pgh.pa.us>, Nathan Bossart <nathandbossart@gmail.com>, Jacob Champion <jacob.champion@enterprisedb.com>, Ignat Remizov <ignat980@gmail.com>, Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2025-12-04T16:32:51Z

Lists: 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.