Re: Create collation reporting the ICU locale display name

From: "Daniel Verite" <daniel(at)manitou-mail(dot)org>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Michael Paquier" <michael(at)paquier(dot)xyz>,"Alvaro Herrera" <alvherre(at)2ndquadrant(dot)com>,pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Create collation reporting the ICU locale display name
Date: 2019-09-14 13:51:03
Message-ID: 1bf35fbd-0560-4b22-99cb-656063016727@manitou-mail.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:

> > This output tend to reveal mistakes with tags, which is why I thought
> > to expose it as a NOTICE. It addresses the case of a user
> > who wouldn't suspect an error, so the "in-your-face" effect is
> > intentional. With the function approach, the user must be
> > proactive.
>
> That argument presupposes (a) manual execution of the creation query,
> and (b) that the user pays close attention to the NOTICE output.
> Unfortunately, I think our past over-use of notices has trained
> people to ignore them.

What about DEBUG1 as the level?
Surely we can draw a line somewhere beyond which the benefit of
getting that information surpasses the annoyance factor that
you're foreseeing?

Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Khandekar 2019-09-14 15:05:25 Re: logical decoding : exceeded maxAllocatedDescs for .spill files
Previous Message Daniel Verite 2019-09-14 13:23:04 Re: Create collation reporting the ICU locale display name