Re: Proposal to provide the facility to set binary format output for specific OID's per session

From: Joe Conway <mail(at)joeconway(dot)com>
To: Jack Christensen <jack(at)jackchristensen(dot)com>, Dave Cramer <davecramer(at)gmail(dot)com>
Cc: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Proposal to provide the facility to set binary format output for specific OID's per session
Date: 2022-07-25 17:30:43
Message-ID: cf1762e4-5d85-a693-26d1-1d6dfa4d111d@joeconway.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 7/25/22 10:07, Jack Christensen wrote:
> The advantage is to be able to use the binary format with only a single
> network round trip in cases where prepared statements are not possible.
> e.g. when using PgBouncer. Using the simple protocol with this patch
> lets users of pgx (the Go driver mentioned above) and PgBouncer use the
> binary format. The performance gains can be significant especially with
> types such as timestamptz that are very slow to parse.
>
> As far as only sending binary types that the client can understand, the
> client driver would call `set format_binary` at the beginning of the
> session.

+1 makes a lot of sense to me.

Dave please add this to the open commitfest (202209)

--
Joe Conway
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2022-07-25 18:27:22 Re: very long record lines in expanded psql output
Previous Message Hamid Akhtar 2022-07-25 17:21:02 Re: Allow pageinspect's bt_page_stats function to return a set of rows instead of a single row