Re: [PATCH 4/4] Add tests to dblink covering use of COPY TO FUNCTION
| От | Pavel Stehule |
|---|---|
| Тема | Re: [PATCH 4/4] Add tests to dblink covering use of COPY TO FUNCTION |
| Дата | |
| Msg-id | 162867790911250023t10503a83qa143955e148c9dc9@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [PATCH 4/4] Add tests to dblink covering use of COPY TO FUNCTION (Jeff Davis <pgsql@j-davis.com>) |
| Ответы |
Re: [PATCH 4/4] Add tests to dblink covering use of COPY
TO FUNCTION
|
| Список | pgsql-hackers |
2009/11/25 Jeff Davis <pgsql@j-davis.com>: > On Wed, 2009-11-25 at 07:36 +0100, Pavel Stehule wrote: >> > Moving records from a function to a table can be done with: >> > INSERT INTO mytable SELECT * FROM myfunc(); >> > And that already works fine. >> >> It works, but COPY FROM myfunc() should be significantly faster. You >> can skip tuple store. > > If SRFs use a tuplestore in that situation, it sounds like that should > be fixed. Why do we need to provide alternate syntax involving COPY? It isn't problem of SRF function design. It allow both mode - row and tuplestor. This is problem of INSERT statement, resp. INSERT INTO SELECT implementation. Regards Pavel > > Regards, > Jeff Davis > >
В списке pgsql-hackers по дате отправления: