Re: When should parameters be passed as text v. binary?

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To: Paula Kirsch <pl(dot)kirsch(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: When should parameters be passed as text v. binary?
Date: 2020-01-04 18:59:06
Message-ID: 87blrjktdo.fsf@news-spur.riddles.org.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>>>>> "Paula" == Paula Kirsch <pl(dot)kirsch(at)gmail(dot)com> writes:

Paula> I'm just trying to understand the trade-offs between sending
Paula> everything always as text, all integer parameters as binary,
Paula> floats as binary, etc.

For passing data from client to server, there's no particular reason not
to use the binary format for any data type that you understand (and
where you're passing the data type oid explicitly in the query, rather
than just leaving it as unknown).

For results, things are harder, because libpq is currently
all-or-nothing about result type formats, and if you start using
extension types then not all of them even _have_ a binary format. And to
decode a binary result you need to know the type, and have code to
handle every specific type's binary format.

--
Andrew (irc:RhodiumToad)

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Justin 2020-01-04 20:30:00 Re: When should parameters be passed as text v. binary?
Previous Message Rich Shepard 2020-01-04 18:27:10 Undeliverable: Re: Changing default ../data/ directory (fwd)