Re: Add support for DEFAULT specification in COPY FROM
Andrew Dunstan <andrew@dunslane.net>
From: Andrew Dunstan <andrew@dunslane.net>
To: Israel Barth Rubio <barthisrael@gmail.com>, Zhihong Yu <zyu@yugabyte.com>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2023-01-09T13:52:41Z
Lists: pgsql-hackers
On 2022-12-02 Fr 09:11, Israel Barth Rubio wrote: > Hello all, > > I'm submitting a new version of the patch. Instead of changing signature > of several functions in order to use the defaults parameter, it is now > storing > that in the cstate structure, which is already passed to all functions > that > were previously modified. > I'm reviewing this and it looks in pretty good shape. I notice that in file_fdw.c:fileIterateForeignScan() we unconditionally generate the estate, switch context etc, whether or not there is a default option used. I guess there's no harm in that, and the performance impact should be minimal, but I thought it worth mentioning, as it's probably not strictly necessary. cheers andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com
Commits
-
Add a DEFAULT option to COPY FROM
- 9f8377f7a279 16.0 landed