Re: postgres_fdw: Use COPY to speed up batch inserts
| От | jian he | 
|---|---|
| Тема | Re: postgres_fdw: Use COPY to speed up batch inserts | 
| Дата | |
| Msg-id | CACJufxFXhAuFDfQS=N0nCaFFTi08__cfwh6E7LhDuuJiAEo=Ww@mail.gmail.com обсуждение исходный текст  | 
		
| Ответ на | Re: postgres_fdw: Use COPY to speed up batch inserts ("Matheus Alcantara" <matheusssilv97@gmail.com>) | 
| Ответы | 
                	
            		Re: postgres_fdw: Use COPY to speed up batch inserts
            		
            		 | 
		
| Список | pgsql-hackers | 
On Sat, Oct 25, 2025 at 2:27 AM Matheus Alcantara
<matheusssilv97@gmail.com> wrote:
>
> On this new version I also added some regress tests on postgres_fdw.sql
>
In the CopyFrom function, we have the CopyInsertMethod, CIM_SINGLE is slower
than CIM_MULTI, I think.
We should do performance tests for the case where the COPY statement is limited
to use CIM_SINGLE.
You can use triggers to make COPY can only use the CIM_SINGLE copymethod.
for example:
create function dummy() returns trigger as $$ begin return new; end $$
language plpgsql;
create trigger dummy
    before insert or update on batch_table_3
    for each row execute procedure dummy();
My local tests show that when batch_size is greater than 2, COPY performs faster
than batch inserts into a foreign table, even though COPY can only use
CIM_SINGLE.
However, my tests were done with an enable-assert build, since I
encountered issues compiling the release build.
anyway, I am sharing my test script.
		
	Вложения
В списке pgsql-hackers по дате отправления: