PQexecParams with binary resultFormat vs BINARY CURSOR - Mailing list pgsql-general

From Mateusz Łoskot
Subject PQexecParams with binary resultFormat vs BINARY CURSOR
Date
Msg-id CABUeae-3rFg2cGM+8P9zc8EdkeoJeuC9at7yda20vwWr3vQ+Kw@mail.gmail.com
Whole thread Raw
Responses Re: PQexecParams with binary resultFormat vs BINARY CURSOR  (Dmitriy Igrishin <dmitigr@gmail.com>)
List pgsql-general
Hi,

Considering query for binary data stored directly in tables
using libpq API, I'm trying to understand what is the difference
between specifying binary format in functions like
PQexecParams and use of BINARY CURSOR.

For example, with query like this:

SELECT large_image FROM tbl;

where large_image is a custom type,
is there a big difference between binary format specified
to libpq and use of BINARY CURSOR?
Is it client-side binary vs server-side binary processing?

Simply, I'd like to avoid textual<->binary conversions at any stage.

(Endianness is not an issue here.)

Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net

pgsql-general by date:

Previous
From: Thom Brown
Date:
Subject: Re: VACUUM touching file but not updating relation
Next
From: Craig Ringer
Date:
Subject: Re: Fedora 16 note...