Bill Thoen <bthoen@gisnet.com> writes:
> Does anyone know what happened and how I can fix it?
Well, you evidently hit a bug, but there's not nearly enough info here
to guess whether the bug is in Postgres, PostGIS, GEOS, or GDAL, or
perhaps in your custom build process for one of these. I'd suggest
installing the debuginfo RPMs for them if you didn't already, collecting
a coredump (you'll need to ensure the postmaster is started with ulimit
-c unlimited) and getting a stack trace from the dump with gdb.
(Alternatively, since it takes awhile to reach the crash, you could just
attach to the running backend with gdb and let it continue to the crash;
that would save fooling with ulimit.) Then send the trace to
pgsql-bugs. You'll need to provide some details about the table and the
query, too.
regards, tom lane
