| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Joel Jacobson <joel(at)compiler(dot)org> |
| Cc: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: New "single" COPY format |
| Date: | 2024-11-08 06:14:02 |
| Message-ID: | CAKFQuwbD+sG4P60Tp3VbrsV7gXfhQViYLy-1n8h+AO_FsAy9hw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thursday, November 7, 2024, Joel Jacobson <joel(at)compiler(dot)org> wrote:
> On Fri, Nov 8, 2024, at 00:13, Masahiko Sawada wrote:
> > In earlier versions, we supported loading the whole file into a single
> > tuple. Is there any reason that it doesn't support it in v18? I think
> > if it's useful we can improve it in a separate patch.
>
> Not sure how useful it is, since we already have pg_read_file().
Being forced to have the file server-readable, non-stdin, destroys quite a
bit of the usefulness of pg_read_file.
If we want clients to be able to pass the effort here to the server, copy
is definitely the most useful way to do so.
I’d be concerned choosing “single” given this future possibility. I do
agree that such an enhancement would be best done in its own patch.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jian he | 2024-11-08 06:44:40 | Re: not null constraints, again |
| Previous Message | Michael Paquier | 2024-11-08 06:08:19 | Re: pg_stat_statements: Avoid holding excessive lock |