Re: something has gone wrong, but what is it?
От
Robert Haas
Тема
Re: something has gone wrong, but what is it?
Дата
Msg-id
CA+TgmoYsqxa38jt9KWY3nYnLzoKt-OTQqYcZ_=CHLCRO=rgfAg@mail.gmail.com
Ответ на
Список
Дерево обсуждения
something has gone wrong, but what is it? Robert Haas <robertmhaas@gmail.com>
Re: something has gone wrong, but what is it? Tom Lane <tgl@sss.pgh.pa.us>
Re: something has gone wrong, but what is it? Robert Haas <robertmhaas@gmail.com>
Re: something has gone wrong, but what is it? Andres Freund <andres@anarazel.de>
Re: something has gone wrong, but what is it? Andrey Borodin <x4mmm@yandex-team.ru>
Re: something has gone wrong, but what is it? Robert Haas <robertmhaas@gmail.com>
Re: something has gone wrong, but what is it? Daniel Gustafsson <daniel@yesql.se>
On Wed, Aug 10, 2022 at 9:53 AM Tom Lane wrote: > Robert Haas writes: > > - elog(ERROR, "something has gone wrong"); > + elog(ERROR, "unrecognized AuxProcType: %d", (int) auxtype); > > +1 ... the existing message is clearly not up to project standard. After a bit of further looking around I noticed that there's another check for an invalid auxtype in this function which uses a slightly different message text and also PANIC rather than ERROR. I think we should adopt that here too, for consistency, as in the attached. The distinction between PANIC and ERROR doesn't really seem to matter here. Either way, the server goes into an infinite crash-and-restart loop. May as well be consistent. -- Robert Haas EDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления