| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
| Cc: | PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [BUGS] BUG #6046: select current_date crashes postgres |
| Date: | 2011-06-01 02:53:47 |
| Message-ID: | 7038.1306896827@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> writes:
> On 1/06/2011 9:01 AM, Craig Ringer wrote:
>> Is anyone aware of any changes between 9.0 and 9.1beta that messed with
>> time zone handling and loading?
> By the way, it looks like using any of:
> SELECT 'now'::timestamp;
> SELECT 'now'::timestamptz;
> SELECT current_time;
> SELECT current_date;
> SELECT localtime;
> SELECT localtimestamp;
> SELECT CAST( now() AS date );
> will also trigger a crash.
This is the known problem with timezone abbreviations not being
initialized correctly on Windows --- anything involving interpreting a
"keyword" in datetime input will go belly up. See commits 2e82d0b39,
e05b86644.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2011-06-01 03:50:38 | Re: BUG #6046: select current_date crashes postgres |
| Previous Message | Craig Ringer | 2011-06-01 01:14:13 | Re: BUG #6046: select current_date crashes postgres |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2011-06-01 02:55:03 | Re: creating CHECK constraints as NOT VALID |
| Previous Message | Tatsuo Ishii | 2011-06-01 02:52:58 | Re: Any idea for serializing INSERTING SERIAL column? |