Re: When extended query protocol ends?
От | Vladimir Sitnikov |
---|---|
Тема | Re: When extended query protocol ends? |
Дата | |
Msg-id | CAB=Je-Hi_48+7gea54bkiKXz6hCFYWj1_WD-3bApFXP=+JG1cw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: When extended query protocol ends? (Jelte Fennema-Nio <postgres@jeltef.nl>) |
Ответы |
Re: When extended query protocol ends?
Re: When extended query protocol ends? |
Список | pgsql-hackers |
>Would performance suffer that much?
I have not benchmarked it much, however, the driver sends "autosave" queries once (savepoint) or twice(savepoint+release) for every user-provided query.
If we use extended queries (parse+bind+exec) for every savepoint, that would result in 3 or 6 messages overhead for every user query.
From many measurements we know that insert into table(id, name) values(?,?),(?,?),(?,?) is much more efficient than
sending individual bind-exec-bind-exec-bind-exec-sync messages like "insert into table(id, name) values(?,?)"
For instance, here are some measurements: https://www.baeldung.com/spring-jdbc-batch-inserts#performance-comparisons
Based on that measurements I assume there's a non-trivial per-message overhead.
Vladimir
В списке pgsql-hackers по дате отправления: