[PATCH] pg_upgrade: Split off pg_fatal() from pg_log()

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема [PATCH] pg_upgrade: Split off pg_fatal() from pg_log()
Дата
Msg-id 1379040642.8575.6.camel@vanquo.pezone.net
обсуждение исходный текст
Ответы Re: [PATCH] pg_upgrade: Split off pg_fatal() from pg_log()  (Marko Tiikkaja <marko@joh.to>)
Re: [PATCH] pg_upgrade: Split off pg_fatal() from pg_log()  (Bruce Momjian <bruce@momjian.us>)
Список pgsql-hackers
The experiences with elog() and ereport() have shown that having one
function that can return or not depending on some log level parameter
isn't a good idea when you want to communicate well with the compiler.
In pg_upgrade, there is a similar case with the pg_log() function.
Since that isn't a public API, I'm proposing to change it and introduce
a separate function pg_fatal() for those cases where the calls don't
return.


Вложения

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

Предыдущее
От: wangshuo@highgo.com.cn
Дата:
Сообщение: Re: ENABLE/DISABLE CONSTRAINT NAME
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: getting rid of maintainer-check