Re: 7.2 and current timestamp bug?

From: Thomas Lockhart <lockhart(at)fourpalms(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: 7.2 and current timestamp bug?
Date: 2002-02-19 06:56:57
Message-ID: 3C71F739.D2E9CD02@fourpalms.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

...
> Another possibility is to allow date2j and j2date to pass/return double
> instead of int, but that is a larger change and probably not very safe
> to apply for 7.2.1.

Pretty sure that j2date() relies on integer math behaviors to work. But
I haven't looked at it in quite a while. And it probably isn't worth the
effort to change things around. Limiting the date range a little works
for me. Lots of DBs allow only four digit years...

> Thomas, your thoughts?

Hmm. Let's yell at Tatsuo for trying silly dates ;)

- Thomas

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark kirkwood 2002-02-19 08:37:45 Transient Disk Usage Higher In 7.2 ?
Previous Message Thomas Lockhart 2002-02-19 06:48:40 Re: Ready to branch 7.2/7.3 ?