Re: hash_create(): check return code
От
Tom Lane
Тема
Re: hash_create(): check return code
Дата
Msg-id
3960.1098429205@sss.pgh.pa.us
Ответ на
Re: hash_create(): check return code (Neil Conway)
Список
Дерево обсуждения
hash_create(): check return code Neil Conway <neilc@samurai.com>
Re: hash_create(): check return code Tom Lane <tgl@sss.pgh.pa.us>
Re: hash_create(): check return code Neil Conway <neilc@samurai.com>
Re: hash_create(): check return code Tom Lane <tgl@sss.pgh.pa.us>
Re: hash_create(): check return code Neil Conway <neilc@samurai.com>
Re: hash_create(): check return code Tom Lane <tgl@sss.pgh.pa.us>
Re: hash_create(): check return code Neil Conway <neilc@samurai.com>
Neil Conway writes: > On Fri, 2004-10-22 at 16:13, Tom Lane wrote: >> There are no places where hash_create is called before elog() is >> functional. > Well, it's invoked from the statistics collector, which avoids doing > elog(ERROR) for some reason. With all due respect to Jan, that coding seems 100% bogus. elog(ERROR) will work (it had better, because pgstat.c certainly calls routines that might do it) and the insistence on using exit() rather than proc_exit() is just plain wrong anyway. Note that there is really no difference between elog(ERROR) and elog(FATAL) in this context, since pgstat doesn't have an outer sigsetjmp call. regards, tom lane
В списке pgsql-patches по дате отправления