Re: [HACKERS] Re: ERROR: index_rescan: invalid amrescan regproc ???

Tom Lane wrote:

> >> You might try building the backend with assert checking turned on
> >> (--enable-cassert) to see if any problems are detected.
>
> > Ok, do I need to set something else? I get the following when I try to run
> > the Java application:
>
> > TRAP: Bad Argument to Function Call("!(AllocSetContains(set, pointer)):",
> > File: "aset.c", Line: 292)
>
> > !(AllocSetContains(set, pointer)) (0) [No such file or directory]
>
> That looks like an assert check to me ... send it along to the hackers
> list, because aset.c is outside what I know about the backend.
> Can you provide a debugger backtrace at that point, by any chance?

(ultra5, Solaris 7, cc: WorkShop Compilers 5.0 98/12/15 C 5.0, jdk1.2.1)

I've configured the pgsql as:

./configure --prefix=/opt/pgsql \
--with-tcl \
--with-includes=/opt/tcl_tk/include \
--with-tclconfig=/opt/tcl_tk/lib \
--with-template=solaris_sparc_cc \
--with-CC=cc \
--enable-cassert \
--with-perl

Then started postmaster as:
su bpm -c "${PGSQLHOME}/bin/postmaster -i -d -D ${PGDATA} 2>&1 >
${PGDATA}/trace.log"

Then ran a Java application to retrieve blobs from a database that I created and
populated. Table def is:
CREATE TABLE item (item_num int PRIMARY KEY, item_picture oid, item_descr text,
ship_unit varchar(15), unit_price money, stock int)

psql yields:

mini_stores=> select * from item;
item_num|item_picture|item_descr
|ship_unit |unit_price|stock
--------+------------+--------------------------------------------------------------+----------+----------+-----

1| 18730|Maximum protection for high-mileage
runners |pair |$75.50 | 1000
2| 18745|Customize your mountain bike with extra-durable
crankset |each |$20.00 | 500
3| 18762|Long drive golf balls -fluorescent
yellow |pack of 12|$50.00 | 200
4| 18780|Your first season's baseball
glove |pair |$25.00 | 250
5| 18796|Minimum chin contact, feather-light, maximum protection
helmet|each |$35.50 | 50
(5 rows)

The Java app is giving errors, so I compiled pgsql with ASSERT_CHECKING enabled,
but I get the following error:

TRAP: Bad Argument to Function Call("!(AllocSetContains(set, pointer)):", File:
"aset.c", Line: 292)

!(AllocSetContains(set, pointer)) (0) [No such file or directory]
/opt/pgsql/bin/postmaster: reaping dead processes...
/opt/pgsql/bin/postmaster: CleanupProc: pid 27783 exited with status 134
/opt/pgsql/bin/postmaster: CleanupProc: reinitializing shared memory and
semaphores

Do I need to configure something else?

The error, 134 is
vlad: checkERR 132
#define ENOBUFS 132 /* No buffer space available */

Thanks.

--
Brian Millett
Enterprise Consulting Group "Heaven can not exist,
(314) 205-9030 If the family is not eternal"
bpm(at)ec-group(dot)com F. Ballard Washburn