Re: using index or check in ALTER TABLE SET NOT NULL
От | David Rowley |
---|---|
Тема | Re: using index or check in ALTER TABLE SET NOT NULL |
Дата | |
Msg-id | CAKJS1f9Gaor9+wGWFwaSrm1=N5cPHiM=LGWcCDeuPymC5dkyhw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: using index or check in ALTER TABLE SET NOT NULL (Sergei Kornilov <sk@zsrv.org>) |
Ответы |
Re: using index or check in ALTER TABLE SET NOT NULL
|
Список | 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 по дате отправления: