Excerpts from Duncan Rance's message of mié feb 01 17:43:48 -0300 2012:
> I mentioned in the bug report that I has asserts in places were t_hoff is
> set. I've been doing it like so:
>
> if (hoff % 4 != 0) {
> elog(ERROR, "wrong hoff: %d",hoff);
> abort();
> }
>
> I've been sitting here waiting for the server to abort and only just realised
> there are some interesting entries in my pgbench logs. I'm using pgbench to
> hammer the server with queries, and I have a handful of these:
elog(ERROR) longjmps to the error handling code and never returns to
your abort() call. If you want it to abort at that point, use elog(PANIC).
Or you could do elog(WARNING) and then abort(), which is pretty much the
same thing.
--
Álvaro Herrera <alvhe...@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
