On Wed, Feb 05, 2025 at 01:36:57PM -0600, Sami Imseih wrote: >> 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.
Given we don't have any other reports or opinions, I'm probably just going to apply the patch to v18. That leaves the door open to back-patch later. The next minor release is next week, anyway, and this doesn't seem urgent. I did find one other thread that mentions this behavior [0]. They floated the idea of blocking COPY FREEZE on foreign tables, but the topic fizzled out in indecision. *shrug* [0] https://postgr.es/m/20181219023814.GA6577%40paquier.xyz -- nathan
