| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Wright, George" <George(dot)Wright(at)infimatic(dot)com> |
| Cc: | "Michael Glaesemann" <grzm(at)seespotcode(dot)net>, pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: timestamp problem |
| Date: | 2007-10-31 19:51:55 |
| Message-ID: | 18865.1193860315@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
"Wright, George" <George(dot)Wright(at)infimatic(dot)com> writes:
> I would expect:
> myhost=> select isfinite(timestamp '2007-10-14 00:00:00 BRST');
> to error out just like:
No, this is intentional behavior. Note the comment in
DetermineTimeZoneOffset:
/*
* It's an invalid or ambiguous time due to timezone transition. Prefer
* the standard-time interpretation.
*/
BTW, isfinite() has got nothing whatever to do with this. If an error
were to be thrown, it would have to be during timestamp value input.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-10-31 21:43:01 | Re: timestamp problem |
| Previous Message | niccguard-dev | 2007-10-31 19:34:08 | What data type best used for money |