| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "energumen(at)buaa(dot)edu(dot)cn" <energumen(at)buaa(dot)edu(dot)cn> |
| Cc: | "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: how can i get the binary format of timestamp? |
| Date: | 2006-04-19 14:52:51 |
| Message-ID: | 26113.1145458371@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"energumen(at)buaa(dot)edu(dot)cn" <energumen(at)buaa(dot)edu(dot)cn> writes:
> if define HAVE_INT64_TIMESTAMP
> result is: 4E66 E642 0030 C274
> if not define HAVE_INT64_TIMESTAMP
> {
> if define INT64_IS_BUSTED result is: 6972 2142 0000 00DB
> if not define INT64_IS_BUSTED result is: 4221 7269 DB00 0000
> }
I think you got your cases mixed up. In the not-HAVE_INT64_TIMESTAMP
case the value would be a float8 and wouldn't be affected at all by
INT64_IS_BUSTED.
Defining both HAVE_INT64_TIMESTAMP and INT64_IS_BUSTED is not supported.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | danish.siddiqui@hovservices.com | 2006-04-19 15:34:10 | parser error when trying to connect to postges db from tomcat |
| Previous Message | Martijn van Oosterhout | 2006-04-19 10:25:30 | Re: concurrent transactions inside the same connection |