Duncan Rance <postgres@dunquino.com> writes:
> 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
mypgbench logs. I'm using pgbench to hammer the server with queries, and I have a handful of these:
> Client 87 aborted in state 8: ERROR: wrong hoff: 134
Yowza. Is this just the standard pgbench test, or something else?
If you could post complete instructions for duplicating this, we
could probably find the cause fairly quickly.
> What I don't get is why this is causing the client to abort, and not the backend.
As Alvaro said, it's not reaching the abort(). You should use PANIC
instead.
regards, tom lane
