pgsql: Don't fail on libpq-generated error reports in pg_amcheck.

Поиск
Список
Период
Сортировка
От Tom Lane
Тема pgsql: Don't fail on libpq-generated error reports in pg_amcheck.
Дата
Msg-id E1nyEdH-00308t-4F@gemulon.postgresql.org
обсуждение исходный текст
Список pgsql-committers
Дерево обсуждения 
Don't fail on libpq-generated error reports in pg_amcheck.

An error PGresult generated by libpq itself, such as a report of
connection loss, won't have broken-down error fields.
should_processing_continue() blithely assumed that
PG_DIAG_SEVERITY_NONLOCALIZED would always be present, and would
dump core if it wasn't.

Per grepping to see if 6d157e7cb's mistake was repeated elsewhere.

Branch
------
REL_14_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/32a85ee46b034be7b8bf8f31b24cf6fe3684fe7f

Modified Files
--------------
src/bin/pg_amcheck/pg_amcheck.c | 2 ++
1 file changed, 2 insertions(+)

В списке pgsql-committers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: pgsql: Don't fail on libpq-generated error reports in ecpg_raise_backen
Следующее
От: Tom Lane
Дата:
Сообщение: pgsql: Fix off-by-one loop termination condition in pg_stat_get_subscri