Re: BUG #18883: Epoch issue

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: "ravi105173(at)gmail(dot)com" <ravi105173(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #18883: Epoch issue
Date: 2025-04-08 12:29:53
Message-ID: CAKFQuwYJvDL7b=a4UGCKpEZHCHTZ4H4T0UST=+uWT6YhoJ+9NQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tuesday, April 8, 2025, PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:

> The following bug has been logged on the website:
>
> Bug reference: 18883
> Logged by: RAVI KANT BHUSHAN
> Email address: ravi105173(at)gmail(dot)com
> PostgreSQL version: 16.1
> Operating system: Windows 10
> Description:
>
> Number of days calculation using EPOCH is not providing right answer:
>
> Query: SELECT (EXTRACT(EPOCH FROM ('2025-04-08 11:25:01'::timestamp -
> '2025-03-13 15:33:30'::timestamp)) / 86400)::INT
> ==> output is 26, but right answer is 25 days
>
>
select 1.75::int; — yields 2

We don’t document the precise rules for what casting does but rounding
seems reasonable. Use the floor function to get your expected answer.

David J.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Kaimeh 2025-04-08 12:38:17 Error when using array_agg with filter where clause in pg16 and pg17
Previous Message PG Bug reporting form 2025-04-08 12:00:14 BUG #18883: Epoch issue