Re: When should parameters be passed as text v. binary?
Adrian Klaver <[email protected]> Sat, 4 Jan 2020 12:42:00 -0800
| Newsgroups | gmane.comp.db.postgresql.general |
|---|---|
| Message-ID | <[email protected]> |
On 1/4/20 11:25 AM, Paula Kirsch wrote: Please reply to list also. Ccing list. > In an extended-query, my understanding is that you can choose to pass > the parameters as text or binary. I am trying to understand > https://www.postgresql.org/docs/current/protocol-flow.html#PROTOCOL-FLOW-EXT-QUERY > and > https://www.postgresql.org/docs/current/protocol-message-formats.html. > Thus the question about the benefits/detriments of passing the > parameters as binary or text. > > I am also having difficulty finding the postgresql documentation for the > data type oid to pass to explicitly type the parameters. https://www.postgresql.org/docs/11/catalog-pg-type.html > > Any suggestions or examples of parse-messages with a couple of > parameters being passed would be appreciated. > > Thank you. > > On Sat, Jan 4, 2020 at 11:18 AM Adrian Klaver <[email protected] > <mailto:[email protected]>> wrote: > > On 1/4/20 3:54 AM, Paula Kirsch wrote: > > I'm just trying to understand the trade-offs between sending > everything > > always as text, all integer parameters as binary, floats as > binary, etc. > > From where to where and using what? > > > -- > Adrian Klaver > [email protected] <mailto:[email protected]> > -- Adrian Klaver [email protected]