Re: Getting rid of SQLValueFunction

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Ian Lawrence Barwick <barwick(at)gmail(dot)com>
Cc: Ted Yu <yuzhihong(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Getting rid of SQLValueFunction
Date: 2022-12-30 05:21:22
Message-ID: Y651UhZh8fJNGZib@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Dec 30, 2022 at 10:57:52AM +0900, Ian Lawrence Barwick wrote:
> I noticed this commit (f193883f) introduces following regressions:
>
> postgres=# SELECT current_timestamp(7);
> WARNING: TIMESTAMP(7) WITH TIME ZONE precision reduced to maximum
> allowed, 6
> ERROR: timestamp(7) precision must be between 0 and 6
>
> postgres=# SELECT localtimestamp(7);
> WARNING: TIMESTAMP(7) precision reduced to maximum allowed, 6
> ERROR: timestamp(7) precision must be between 0 and 6
>
> Suggested fix attached.

Thanks for the report, Ian. Will fix.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Richard Guo 2022-12-30 08:05:55 Re: Removing redundant grouping columns
Previous Message Thomas Munro 2022-12-30 03:59:03 Re: CI and test improvements