From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
---|---|
To: | PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [BUGS] BUG #6046: select current_date crashes postgres |
Date: | 2011-06-01 01:13:25 |
Message-ID: | 4DE59235.5000608@postnewspapers.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
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. However, none of these statements do:
SELECT current_timestamp;
SELECT now();
SELECT now() :: timestamptz;
SELECT now() :: timestamp;
--
Craig Ringer
Tech-related writing at http://soapyfrogs.blogspot.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2011-06-01 01:14:13 | Re: BUG #6046: select current_date crashes postgres |
Previous Message | Craig Ringer | 2011-06-01 01:01:55 | Re: [BUGS] BUG #6046: select current_date crashes postgres |
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2011-06-01 01:14:13 | Re: BUG #6046: select current_date crashes postgres |
Previous Message | Cédric Villemain | 2011-06-01 01:11:16 | Re: [PERFORM] Hash Anti Join performance degradation |