Re: Prevent COPY FREEZE on Foreign tables

From: Sami Imseih <samimseih(at)gmail(dot)com>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: Zhang Mingli <zmlpostgres(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Prevent COPY FREEZE on Foreign tables
Date: 2025-02-05 19:36:57
Message-ID: CAA5RZ0sqU2To+yZPXAzUwNMsWdNGwhwBBEFmqp6jxxG6Sr-6Eg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> so the only reason I can see
> for not back-patching it is that it could lead to somewhat widespread
> breakage for existing scripts, etc. which are arguably kind-of working
> today.

That is my thought for not backpatching. It's not breaking the COPY
command, it's just not applying an optimization.

Let's see what others think.

Sami

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2025-02-05 19:46:05 Re: Failed assertion with jit enabled
Previous Message Jelte Fennema-Nio 2025-02-05 19:36:30 Re: Windows CFBot is broken because ecpg dec_test.c error