Re: Remove inconsistent quotes from date_part error - Mailing list pgsql-hackers

From Nikhil Benesch
Subject Re: Remove inconsistent quotes from date_part error
Date
Msg-id CAPWqQZSDtV5px+zpQSTtuWHNyf4mUVQzhigrXWtep7_kjhPVXg@mail.gmail.com
Whole thread Raw
In response to Re: Remove inconsistent quotes from date_part error  (Nikhil Benesch <nikhil.benesch@gmail.com>)
Responses Re: Remove inconsistent quotes from date_part error
List pgsql-hackers
Updated patch attached.

On Mon, Jan 3, 2022 at 10:26 AM Nikhil Benesch <nikhil.benesch@gmail.com> wrote:
>
> On Mon, Jan 3, 2022 at 10:20 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > BTW, if you want to get rid of the quotes, I think that something
> > else has to be done to set off the type name from the rest.  In
> > this instance someone might think that we're complaining about a
> > "time zone unit", whatever that is.  I suggest swapping it around to
> >
> >         units \"%s\" not recognized for type %s
> >
> > Also, personally, I'd write unit not units, but that's
> > more debatable.
>
> Your suggestion sounds good to me. I'll update the patch with that.
>
> Not that it changes anything, I think, but the wording ambiguity you
> mention is present today in the timestamptz error message:
>
>     benesch=> select extract('nope' from now());
>     ERROR:  timestamp with time zone units "nope" not recognized

Attachment

pgsql-hackers by date:

Previous
From: Stanislav Bashkyrtsev
Date:
Subject: PostgreSQL stops when adding a breakpoint in CLion
Next
From: Tom Lane
Date:
Subject: Re: Clarify planner_hook calling convention