Re: PG Seg Faults Performing a Query

From: Bill Thoen <bthoen(at)gisnet(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: PG Seg Faults Performing a Query
Date: 2007-08-22 12:44:51
Message-ID: 20070822124451.GA10321@www.gisnet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On Tue, Aug 21, 2007 at 04:38:42PM -0500, Scott Marlowe wrote:
> On 8/21/07, Bill Thoen <bthoen(at)gisnet(dot)com> wrote:
> > How would you suggest I try to track down this problem?
> > I run the following query:
> >
> > SELECT a.* FROM compliance_2006 a, ers_regions b
> > WHERE a.fips_st_cd=b.fips_st
> > AND a.fips_cnty_cd=b.fips_cou AND b.region =1
> > AND a.fips_st_cd='17' AND a.fips_cnty_cd='003';
> >
> > and it works. But when I try this:
> >
> > SELECT a.* FROM compliance_2006 a, ers_regions b
> > WHERE a.fips_st_cd=b.fips_st
> > AND a.fips_cnty_cd=b.fips_cou AND b.region =1
> > AND a.fips_st_cd='17' ;
> >
> > psql dies with the message:
> > Segmentation Fault.
>
> so the client psql is what's dieing right? In that case you likely
> are getting too big a result set for psql to handle at once. Trying
> declaring a cursor to hold your query and fetching 100 or 1000 or so
> rows at a time.
>
> Just guessing. What's the exact text of the error message?
>

The exact message was:

Segmentation Fault.

But the table compliance_2006 is very big (18 million plus records) so I'll
try that cursor idea. But even so, an error like that makes me think that
something's broken.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Patrick Lindeman 2007-08-22 12:54:03 could not open file "pg_clog/0BFF"
Previous Message Russell Smith 2007-08-22 11:23:09 Re: raw data into table process

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2007-08-22 12:47:09 Re: tsearch2 patch status report
Previous Message Teodor Sigaev 2007-08-22 12:20:29 Re: pgsql: Simplify the syntax of CREATE/ALTER TEXT SEARCH DICTIONARY by