Re: using index or check in ALTER TABLE SET NOT NULL - Mailing list pgsql-hackers

From David Rowley
Subject Re: using index or check in ALTER TABLE SET NOT NULL
Date
Msg-id CAKJS1f9Gaor9+wGWFwaSrm1=N5cPHiM=LGWcCDeuPymC5dkyhw@mail.gmail.com
Whole thread Raw
In response to Re: using index or check in ALTER TABLE SET NOT NULL  (Sergei Kornilov <sk@zsrv.org>)
Responses Re: using index or check in ALTER TABLE SET NOT NULL  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, 2 May 2019 at 06:18, Sergei Kornilov <sk@zsrv.org> wrote:
>
> > I proposed that we didn't need those messages at all, which Robert pushed
> > back on, but I'd be willing to compromise by reducing them to NOTICE or
> > DEBUG level.
>
> I posted patch with such change in a separate topic: https://commitfest.postgresql.org/23/2076/
>
> PS: not think this is blocker for v12

Probably not a blocker, but now does not seem like an unreasonable
time to lower these INFO messages down to DEBUG. If not, then we can
just remove the item from the open items list. I just put it there as
I didn't want it getting forgotten about as it wasn't going to be
anybody's priority to think hard about it on the final few days of the
last commitfest of the release.

-- 
 David Rowley                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: REINDEX INDEX results in a crash for an index of pg_class since 9.6
Next
From: Tatsuo Ishii
Date:
Subject: Re: PostgreSQL Asian language support for full text search usingICU (and also updating pg_trgm)