My first guess would be that your select has a few OR's in it (if so
break it up into UNOIN's). If not it would be nice if you would send
the statement so that we might give you pointers in rewriting it.
> -----Original Message-----
> From: Michael Olivier [SMTP:molivier(at)yahoo(dot)com]
> Sent: Sunday, October 25, 1998 11:13 PM
> To: pgsql-sql(at)postgreSQL(dot)org
> Subject: [SQL] palloc failure: memory exhausted, but ulimit
> I'm running postgresql-6.3.2-10 under RH Linux 5.1, and have a small
> database (6 tables with hundreds of records each) on which I'm getting
> the error
> FATAL 1: palloc failure: memory exhausted
> ...on a complex select statement. I read in the FAQ that I need to up
> ulimit, but as user 'michael', 'postgres', or 'root', when I type
> 'ulimit' at the bash prompt, it says 'unlimited'. I'm running on a
> 350MHz PC with 96 MB RAM and a 100 MB swap space. Other apps running
> are Apache, netscape client, and emacs.
> Any suggestions for me? I've also searched email archives and dejanews
> but haven't found my answer.
> My select query has a number of conditions in the 'where' clause, and
> I'm wondering if I need to break them out into separate selects into
> temporary tables. I tried breaking them into several temporary views
> but got the same result.
> thanks for your help!
> DO YOU YAHOO!?
> Get your free @yahoo.com address at http://mail.yahoo.com
pgsql-sql by date
|Next:||From: Brenda Butler||Date: 1998-10-27 02:16:49|
|Previous:||From: Herouth Maoz||Date: 1998-10-26 14:57:39|
|Subject: Re: [SQL] idiom to mv recs => [NEW] bleeding lock?|