Re: default result formats setting - Mailing list pgsql-hackers

From Dave Cramer
Subject Re: default result formats setting
Date
Msg-id CADK3HHJJUvLUC-kvVJYuEsyR8ucVtOsHDHudDcyWmxvdx2aefQ@mail.gmail.com
Whole thread Raw
In response to Re: default result formats setting  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers


On Sun, 7 Aug 2022 at 09:58, Robert Haas <robertmhaas@gmail.com> wrote:
On Wed, Mar 24, 2021 at 12:01 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I don't think I buy the premise that there are exactly two levels
> on the client side.

Thanks for sharing your thoughts on this. I agree it's a complex
issue, and the idea that there are possibly more than two logical
levels is, for me, maybe your most interesting observation.

--
Robert Haas
EDB: http://www.enterprisedb.co

I'd like to revive this thread.

I have put in a patch to do the same thing.

Upthread Tom mused about how the JDBC driver would handle it. I can tell you that it handles it fine with no changes as does the go driver. Further as Jack pointed out it provides significant performance benefits.

The original discussion correctly surmises that the DESCRIBE statement is rarely (if ever) used as any advantages of sending are nullified by the cost of sending it.

I prefer the GUC as this allows pools to be configured to reset the setting when returning the connection to the pool and setting it correctly for the client when borrowing the connection.

Regards,

Dave

 

pgsql-hackers by date:

Previous
From: Marcos Pegoraro
Date:
Subject: bug on log generation ?
Next
From: Tom Lane
Date:
Subject: Re: bug on log generation ?