Re: [HACKERS] COPY as a set returning function
| От | Corey Huinker |
|---|---|
| Тема | Re: [HACKERS] COPY as a set returning function |
| Дата | |
| Msg-id | CADkLM=ecT6kp+ZKz7M3zgj=LjjAsuJqYpVppb=z=N19SMouC4Q@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [HACKERS] COPY as a set returning function (David Fetter <david@fetter.org>) |
| Список | pgsql-hackers |
On Wed, Jan 25, 2017 at 1:10 PM, David Fetter <david@fetter.org> wrote:
On Wed, Jan 25, 2017 at 12:23:23PM -0500, Corey Huinker wrote:
>
> Feel free to mark it returned as feedback. The concept didn't
> generate as much enthusiasm as I had hoped, so I think the right
> thing to do now is scale it back to a patch that makes
> CopyFromRawFields() externally visible so that extensions can use
> them.
You're getting enthusiasm in the form of these reviews and suggestions
for improvement. That it doesn't always happen immediately is a
byproduct of the scarcity of developer time and the sheer volume of
things to which people need to pay attention.
True about that. I was referring to "ooh! I need that!"-type interest. I'll proceed, keeping in mind that there's a fallback position of just making some of the guts of COPY available to be called by extensions like was done for file_fdw.
В списке pgsql-hackers по дате отправления: