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: pgsql-bugs(at)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: BUG #6425: Bus error in slot_deform_tuple
Date: 2012-02-02 21:44:10
Message-ID: 4909.1328219050@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
Duncan Rance <postgres(at)dunquino(dot)com> writes:
> At last I have been able to reproduce this problem in a relatively simple (yet contrived) way.

> I've put together a tarball with a few scripts, some to be run on the primary and others to be run on the hot-stanby. There's a README in there explaining what to do.

So far no luck reproducing any issue with this test case.  I am running
two copies of import_loop.sh against the master, per your instructions,
and see occasional deadlock errors there as expected.  No errors at all
on the standby though.

One question probably worth asking is what non-default GUC settings are
you using on the master and standby?

(BTW, for anyone else trying this: with multiple copies of
import_loop.sh you will get a lot of "duplicate key" failures with the
test as written.  I had better luck after changing import.sh from
	ts=$(perl -e 'print time')
to
	ts=$$
ie use PID not timestamp as the pseudo-unique key.  This could be made
more bulletproof yet, but it didn't seem worth more trouble.)

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2012-02-02 21:56:30
Subject: Re: BUG #6425: Bus error in slot_deform_tuple
Previous:From: Oleg BartunovDate: 2012-02-02 21:26:13
Subject: NULL's support in SP-GiST

pgsql-bugs by date

Next:From: Tom LaneDate: 2012-02-02 21:56:30
Subject: Re: BUG #6425: Bus error in slot_deform_tuple
Previous:From: Duncan RanceDate: 2012-02-02 18:28:12
Subject: Re: BUG #6425: Bus error in slot_deform_tuple

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