Re: computing completion tag is expensive for pgbench -S -M prepared - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: computing completion tag is expensive for pgbench -S -M prepared
Date
Msg-id CANP8+j+c-bfg7ZrxjtJPuEHf4ykco7RdqbUsXznyhj0+iLHXgw@mail.gmail.com
Whole thread Raw
In response to Re: computing completion tag is expensive for pgbench -S -M prepared  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: computing completion tag is expensive for pgbench -S -M prepared
List pgsql-hackers
On 7 June 2018 at 20:27, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Simon Riggs <simon@2ndquadrant.com> writes:
>> If we're going to compress the protocol, it seems sensible to remove
>> extraneous information first.
>
> Breaking the wire protocol was nowhere in this thread.

No, it wasn't. But there is another thread on the subject of
compressing libpq, which is what I was referring to.

Andres' patch is clearly very efficient at adding the SELECT tag. I am
questioning if we can remove that need altogether.

-- 
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: computing completion tag is expensive for pgbench -S -M prepared
Next
From: Peter Eisentraut
Date:
Subject: cursors with prepared statements