| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Francisco Reyes <lists(at)natserv(dot)com> |
| Cc: | pgsql General List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Troubleshooting cored dumps |
| Date: | 2002-04-19 17:45:13 |
| Message-ID: | 1673.1019238313@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Francisco Reyes <lists(at)natserv(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oberpriller, Wade D. | 2002-04-19 17:56:00 | Disabling libpq clients stderr output from backend |
| Previous Message | Roy Souther | 2002-04-19 17:15:21 | Re: Paradox to PostgreSQL? |