On Thu, Sep 12, 2013 at 10:50:42PM -0400, Peter Eisentraut wrote: > 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.
Fine with me. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
