Skip site navigation (1) Skip section navigation (2)

Re: BUG #6425: Bus error in slot_deform_tuple

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Duncan Rance <postgres(at)dunquino(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6425: Bus error in slot_deform_tuple
Date: 2012-02-01 21:43:34
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugspgsql-hackers
Duncan Rance <postgres(at)dunquino(dot)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 my pgbench 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

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Jim NasbyDate: 2012-02-01 22:12:58
Subject: Re: Progress on fast path sorting, btree index creation time
Previous:From: Alvaro HerreraDate: 2012-02-01 21:05:29
Subject: Re: BUG #6425: Bus error in slot_deform_tuple

pgsql-bugs by date

Next:From: Tom LaneDate: 2012-02-01 21:48:35
Subject: Re: BUG #6426: Complex query runs 10 times longer with "LIMIT 20"
Previous:From: Tom LaneDate: 2012-02-01 21:06:27
Subject: Re: BUG #6200: standby bad memory allocations on SELECT

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group