| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kelly Burkhart <kelly(dot)burkhart(at)gmail(dot)com> |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, 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 15:19:26 |
| Message-ID: | 16741.1298992766@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Kelly Burkhart <kelly(dot)burkhart(at)gmail(dot)com> writes:
> On Mon, Feb 28, 2011 at 8:42 AM, Merlin Moncure <mmoncure(at)gmail(dot)com> 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
> I don't see any libpq calls that can, at run-time, tell you things
> like what format the timestamp is and what endian-ness the server is.
> Is there something I'm missing?
The timestamp format can be determined by querying PQparameterStatus
for the value of "integer_datetimes". Server endianness is irrelevant
because values are always sent big-endian.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-03-01 15:24:08 | Re: database is bigger after dump/restore - why? (60 GB to 109 GB) |
| Previous Message | Adrian Klaver | 2011-03-01 15:18:50 | Re: database is bigger after dump/restore - why? (60 GB to 109 GB) |