Tom,
> A backend coredump is certainly not your fault. Please get a stack
Never underestimate the stupidly of your users. I have a trigger function
which I had not re-compiled, just copied over. I thought of this when
dumping the schema. It's working now.
Sorry for the bandwidth.
Sheepishly yours,
Rob
> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Sent: Friday, November 09, 2001 5:15 PM
> To: Creager, Robert S
> Cc: 'Bugs - PGSQL'
> Subject: Re: [BUGS] signal 10 (SIGBUS) using 7.2b2 Solaris
>
>
> "Creager, Robert S" <CreagRS@LOUISVILLE.STORTEK.COM> writes:
> > Having problems with the dB. Regression tests work, and an online
> > pg_dumpall from 7.1.3 to 7.2b2 worked fine. This dB is
> live on 7.1.3.
> > Using DBD::Pg in a script, although I check the actions
> through psql, with
> > the same results. Could this be me, or the dB?
>
> A backend coredump is certainly not your fault. Please get a stack
> backtrace from the core file and post it. Also please supply
> the schema
> for the table that's accessed by the failing query.
>
> > ./configure --with-tcl --with-tclconfig=/proj/twolf/local/lib
> > --with-includes=/proj/twolf/local/include
> --with-libs=/proj/twolf/local/lib
> > --with-cassert --with-debug --enable-depend
>
> I believe those switches need to be --enable-cassert and
> --enable-debug,
> not --with. This isn't causing your problem but it might impede
> debugging it, since you've got a non-debug build.
>
> regards, tom lane
>