| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
| Cc: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>, davecramer(at)postgres(dot)rocks, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: When extended query protocol ends? |
| Date: | 2024-02-21 16:18:42 |
| Message-ID: | 84852.1708532322@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> writes:
>> 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.
Those should get bundled into single TCP messages, though. Assuming
that that's done properly, I share the doubt that you're saving
anything very meaningful.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David E. Wheeler | 2024-02-21 16:51:59 | Re: Patch: Add parse_type Function |
| Previous Message | Vladimir Sitnikov | 2024-02-21 16:07:20 | Re: When extended query protocol ends? |