| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Steve Chavez <steve(at)supabase(dot)io> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Support a`--with-copy-program` compile flag |
| Date: | 2025-11-12 19:56:10 |
| Message-ID: | aRTmWj4NcYuQDgCq@nathan |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Nov 12, 2025 at 01:07:27PM -0500, Steve Chavez wrote:
> So I wonder if we could remove the possibility of shell access by providing
> a `--with-copy-program` compile flag.
You might be interested in this past discussion for a similar idea:
https://postgr.es/m/flat/20220520225619.GA876272%40nathanxps13
As others have already pointed out, there's no real boundary between
database superusers and the OS user running Postgres. I think many would
like there to be one, but I'm unaware of any serious efforts in that area,
and I doubt there's much appetite for it in the community.
--
nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arseniy Mukhin | 2025-11-12 19:56:58 | Re: Use streaming read I/O in BRIN vacuuming |
| Previous Message | Heikki Linnakangas | 2025-11-12 19:39:47 | Re: LISTEN/NOTIFY bug: VACUUM sets frozenxid past a xid in async queue |