Postgresql Segfault in 8.1 - Mailing list pgsql-general

From Benjamin Smith
Subject Postgresql Segfault in 8.1
Date
Msg-id 200601241717.43533.lists@benjamindsmith.com
Whole thread Raw
Responses Re: Postgresql Segfault in 8.1  (Doug McNaught <doug@mcnaught.org>)
Re: Postgresql Segfault in 8.1  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
I'm running PostgreSQL 8.1 on CentOS 4.2, Dual proc Athlon 64 w/4 GB RAM.

I'm trying to get a PHP app to work, but the failure happens when the command
is copy/pasted into pgsql. Trying to run a large insert statement, and I get:

server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.
#

in /var/log/messages, I see

Jan 24 17:00:04 kepler kernel: postmaster[26185]: segfault at 000000002516d728
rip 000000000043c82c rsp 0000007fbfffddd0 error 4

The insert statement is long, but doesn't seem to violate anything strange -
no weird characters, and all the fields have been properly escaped with
pg_escape().

What information do you need to help figure this out?

-Ben
--
"The best way to predict the future is to invent it."
- XEROX PARC slogan, circa 1978

pgsql-general by date:

Previous
From: "Foster, Stephen"
Date:
Subject: Re: Setting expire date on insert/modify
Next
From: Michael Glaesemann
Date:
Subject: Re: Setting expire date on insert/modify