PQexecParams with binary resultFormat vs BINARY CURSOR

From: Mateusz Łoskot <mateusz(at)loskot(dot)net>
To: pgsql-general(at)postgresql(dot)org
Subject: PQexecParams with binary resultFormat vs BINARY CURSOR
Date: 2011-11-11 02:14:18
Message-ID: CABUeae-3rFg2cGM+8P9zc8EdkeoJeuC9at7yda20vwWr3vQ+Kw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Craig Ringer 2011-11-11 02:56:42 Re: Fedora 16 note...
Previous Message Thom Brown 2011-11-11 01:18:41 Re: VACUUM touching file but not updating relation