Bug 68316 - postgresql fails to format pre-eoch dates
Summary: postgresql fails to format pre-eoch dates
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: postgresql
Version: limbo
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Trond Eivind Glomsrxd
QA Contact: David Lawrence
URL: https://bugzilla.redhat.com/bugzilla/...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-07-09 02:31 UTC by Need Real Name
Modified: 2007-04-18 16:43 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-07-09 02:31:29 UTC
Embargoed:

Attachments (Terms of Use)

Description Need Real Name 2002-07-09 02:31:25 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020625

Description of problem:
This bug is identical to 7.3's bug # 65227, which was triggered by glibc 2.2.5's
ISO-compliance idiocy w.r.t. mktime.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. set up postgresql/postmaster, and start service...
2. enter sql monitor 'psql'
3. run the query: 
	select '6/6/1966'::date::timestamp;

Actual Results:  Query fails with error:

ERROR:  Unable to convert date to tm

Expected Results:  Should return one row:
        ?column?        
------------------------
 1966-06-06 00:00:00-04
(1 row)


Additional info:

This is a show-stopper, it breaks our systems which handle employee birth dates.
Comment 1 Trond Eivind Glomsrxd 2002-07-09 14:50:34 UTC 
foo=# select '6/6/1966'::date;
    date
------------
 1966-06-06
(1 row)

TZ information before 1970 is not supported by the standardard.
Note You need to log in before you can comment on or make changes to this bug.