Re: Troubleshooting cored dumps - Mailing list pgsql-general

From Tom Lane
Subject Re: Troubleshooting cored dumps
Date
Msg-id 1673.1019238313@sss.pgh.pa.us
Whole thread Raw
In response to Troubleshooting cored dumps  (Francisco Reyes <lists@natserv.com>)
Responses Re: Troubleshooting cored dumps
List pgsql-general
Francisco Reyes <lists@natserv.com> writes:
> How does one go about troubleshooting Core Dumps?
> server sent data ("D" message) without prior row description ("T" message)
> server sent data ("D" message) without prior row description ("T" message)
> server sent data ("D" message) without prior row description ("T" message)
> server sent data ("D" message) without prior row description ("T" message)
> server sent data ("D" message) without prior row description ("T" message)
> server sent data ("D" message) without prior row description ("T" message)
> DEBUG:  pq_flush: send() failed: Broken pipe
> Segmentation fault (core dumped)

I'll save you the trouble: I'll bet that psql ran out of memory for a
huge result set.  libpq is not real robust about coping with that :-(.

            regards, tom lane

pgsql-general by date:

Previous
From: Roy Souther
Date:
Subject: Re: Paradox to PostgreSQL?
Next
From: "Oberpriller, Wade D."
Date:
Subject: Disabling libpq clients stderr output from backend