Re: Unstable timestamp binary representation?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Shachar Shemesh <psql(at)shemesh(dot)biz>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Unstable timestamp binary representation?
Date: 2005-03-18 15:20:47
Message-ID: 6678.1111159247@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Shachar Shemesh <psql(at)shemesh(dot)biz> writes:
> In other words, it seems that I, as a client, needs to guess whether
> postgres was compiled with or without "HAVE_INT64_TIMESTAMP".

No, you need to inquire of the value of the "integer_datetimes"
parameter. (At least as of 8.0, this is provided "for free" during
connection startup, so you don't even need an extra network round
trip to find it out.)

> Reading from the actual code, it seems each instance of postgres just
> assumes that it was encoded in the same format as it was compiled with,

No, it checks. See pg_control.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-03-18 15:26:35 Re: QueryResults from Executor
Previous Message Tom Lane 2005-03-18 15:13:02 Re: "they only drink coffee at dec"