| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Steve Crawford <scrawford(at)pinpointresearch(dot)com>, PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Unexpected date conversion results |
| Date: | 2025-11-22 00:43:19 |
| Message-ID: | 2e2a34695d84a297e62a2996466fecf97005a2fb.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, 2025-11-21 at 16:38 -0800, Adrian Klaver wrote:
> > There was a time, like version 9-dot-something, when the above queries
> > performed as expected returning midnight in the current time zone but I
> > haven't been able to find a change document indicating this as an
> > expected change.
>
> I don't remember that, but as the gray content of the hair increases the
> memory is less solid:)
I dug into the git history, and it has been like that since commit b3506006b564
in 2002 (way before version 9.x). That commit fixed a bug that returned ten
time the correct reault (but still offset from the UTC epoch).
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-11-22 00:51:24 | Re: Unexpected date conversion results |
| Previous Message | Adrian Klaver | 2025-11-22 00:38:10 | Re: Unexpected date conversion results |