Re: New "single" COPY format
| От | David G. Johnston |
|---|---|
| Тема | Re: New "single" COPY format |
| Дата | |
| Msg-id | CAKFQuwbD+sG4P60Tp3VbrsV7gXfhQViYLy-1n8h+AO_FsAy9hw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: New "single" COPY format ("Joel Jacobson" <joel@compiler.org>) |
| Ответы |
Re: New "single" COPY format
|
| Список | pgsql-hackers |
On Thursday, November 7, 2024, Joel Jacobson <joel@compiler.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.
В списке pgsql-hackers по дате отправления: