Re: BUG #12432: date_trunc returning wrong year and day

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: bquirion(at)gmail(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #12432: date_trunc returning wrong year and day
Date: 2015-01-05 20:30:31
Message-ID: 4787.1420489831@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

bquirion(at)gmail(dot)com writes:
> foodb=> select date_trunc('week', now() - interval '1 week');
> date_trunc
> ------------------------
> 2013-12-30 00:00:00-08
> (1 row)

> foodb=> select date_trunc('week', now() - interval '2 week');
> date_trunc
> ------------------------
> 2014-12-22 00:00:00-08
> (1 row)

Works for me ...

> I'mn using postgres 8.0.3

A quick look in the commit logs finds an 8.0.4 fix that seems likely
to be the same thing:

Author: Bruce Momjian <bruce(at)momjian(dot)us>
Branch: REL8_0_STABLE Release: REL8_0_4 [0a056c371] 2005-07-04 14:12:45 +0000

Fix date_trunct for December dates that are in the next year, e.g.:
SELECT date_trunc('week', '2002-12-31'::date);
Backpatch to 8.0.X.
Per report from Nick Johnson.

You do realize that (1) 8.0.x has been out of support for more than
four years, and (2) the last release in that series was 8.0.26?
You will not get a lot of traction from filing bug reports against
ten-year-old releases.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Marc Munro 2015-01-05 21:15:05 pg_dump failure with 9.3 server
Previous Message Alvaro Herrera 2015-01-05 20:25:58 Re: BUG #12432: date_trunc returning wrong year and day