Re: Unexpected casts while using date_trunc() - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Unexpected casts while using date_trunc()
Date
Msg-id 915.1527190293@sss.pgh.pa.us
Whole thread Raw
In response to Re: Unexpected casts while using date_trunc()  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
Responses Re: Unexpected casts while using date_trunc()  (Chris Bandy <bandy.chris@gmail.com>)
List pgsql-hackers
Andrew Gierth <andrew@tao11.riddles.org.uk> writes:
> "Tom" == Tom Lane <tgl@sss.pgh.pa.us> writes:
>  Tom> Yeah.  There are two relevant variants of date_trunc():
>  [...]
>  Tom> So we probably ought to change the docs here.

> There's also the option of adding an explicit function
> date_trunc(text,date) returns date, which is a workaround that I (and
> probably quite a few other people) have used. I think having such a
> function added to core would be less surprising than the current
> behavior.

Ah!  Yes, of course, that would be better.  Seems like a workable
solution for Chris, too.  We still can't back-patch it, though.

            regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: contrib/sepgsql fails on Fedora 28
Next
From: Pierre-Emmanuel André
Date:
Subject: PostgreSQL 11 beta1 : regressions failed on OpenBSD with JIT