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

From: Michael Banck <mbanck(at)gmx(dot)net>
To: Kirill Reshke <reshkekirill(at)gmail(dot)com>
Cc: Ignat Remizov <ignat980(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] Add enable_copy_program GUC to control COPY PROGRAM
Date: 2025-12-05 09:30:46
Message-ID: 20251205093046.GE20207@p46.dedyn.io;lightning.p46.dedyn.io
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Fri, Dec 05, 2025 at 12:38:16PM +0500, Kirill Reshke wrote:
> On Fri, 5 Dec 2025, 12:32 Michael Banck, <mbanck(at)gmx(dot)net> wrote:
> The idea here is that you get OOM which will lead to restart.

Right, but you only get OOM if you have memory overcommit enabled (or
are running Postgres in a cgroupv2 container) was my point. Otherwise,
you just get an error:

postgres=# SET work_mem = '1.995TB';
SET
postgres=# select repeat('a',1024*1024*1023) from generate_series(1, 100);
out of memory for query result
postgres=# SELECT 1;
?column?
----------
1
(1 row)

> Aslo you can change archive command to 'shutdown'.

Yeah.

Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2025-12-05 09:49:25 Re: IPC/MultixactCreation on the Standby server
Previous Message Amit Kapila 2025-12-05 09:29:54 Re: Proposal: Conflict log history table for Logical Replication