| From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Binary params in libpq |
| Date: | 2011-03-01 04:41:22 |
| Message-ID: | 4D6C78F2.6040300@postnewspapers.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 28/02/2011 10:42 PM, Merlin Moncure wrote:
> Actually, this has always been a compile time option on the server as
> far as i remember and there is protocol support for it -- libpq tells
> you how it has been set...you've always had to deal with this
> (libpqtypes, which I've mentioned several times as the correct way to
> 'do' binary with libpq, handles this for you). Only the default
> setting was changed.
Ah. Thanks for clarifying that.
It sounds like binary transfer is best for date, timestamp, and bytea.
--
Craig Ringer
Tech-related writing at http://soapyfrogs.blogspot.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksey Tsalolikhin | 2011-03-01 05:51:10 | Re: database is bigger after dump/restore - why? (60 GB to 109 GB) |
| Previous Message | David Johnston | 2011-03-01 01:13:25 | Re: Lock ACCESS EXCLUSIVE and Select question ! |