Re: PG Seg Faults Performing a Query - Mailing list pgsql-general

From Tom Lane
Subject Re: PG Seg Faults Performing a Query
Date
Msg-id 14623.1187829319@sss.pgh.pa.us
Whole thread Raw
In response to Re: PG Seg Faults Performing a Query  (Bill Thoen <bthoen@gisnet.com>)
List pgsql-general
Bill Thoen <bthoen@gisnet.com> writes:
> As you requested, here's what bt in gbd reports:
> (gdb) bt
> #0  0x0000003054264571 in fputc () from /lib64/libc.so.6
> #1  0x000000000040dbd2 in print_aligned_text ()
> #2  0x000000000040f10b in printTable ()
> #3  0x000000000041020b in printQuery ()
> #4  0x0000000000407906 in SendQuery ()
> #5  0x0000000000409153 in MainLoop ()
> #6  0x000000000040b16e in main ()

Hmph.  So it looks like it successfully absorbed the query result from
the backend and is dying trying to print it.

What this smells like to me is someplace failing to check for a malloc()
failure result, but I don't see any such places in print.c.  And I
didn't have any luck reproducing the problem while exercising 8.1 psql
on 64-bit Fedora 6.  I got either "out of memory for query result" or
plain "out of memory", nothing else.

Can you install the postgresql debuginfo RPM, or reproduce this on a
custom build with debugging enabled?  Knowing just where the crash
is might help more.

            regards, tom lane

pgsql-general by date:

Previous
From: "Scott Marlowe"
Date:
Subject: Re: Postgres, fsync and RAID controller with 100M of internal cache & dedicated battery
Next
From: John DeSoi
Date:
Subject: Re: reporting tools