tables are not that large...
essentially we are working on a tool for someone to be able to slice and
dice their database any which way they
want. Thus it allows users to create really ugly SQL with a bunch of AND/OR
joins. I am currently running on
a box with 128M. I have tried ulimit -s unlimited to unlimit the stack size
(didn't help), tried setting -B (buffer size to 256 and 1024 to no avail).
- Greg
-----Original Message-----
From: The Hermit Hacker [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 11, 2000 5:01 PM
To: Gregory Krasnow
Cc: [EMAIL PROTECTED]
Subject: RE: [GENERAL] backend running out of memory in v7.0
okay, well, you ask for a recommended configuration, but how about
throwing yours out at us, and we can try and suggestion areas where you
could improve vs doing it all at once? :) btw ... what are the sizes of
your tables/databases?
On Thu, 11 May 2000, Gregory Krasnow wrote:
> [postgres@warpfactor2 pgsql]$ ulimit -a
> core file size (blocks) 0
> data seg size (kbytes) unlimited
> file size (blocks) unlimited
> max locked memory (kbytes) unlimited
> max memory size (kbytes) unlimited
> open files 1024
> pipe size (512 bytes) 8
> stack size (kbytes) 8192
> cpu time (seconds) unlimited
> max user processes 2048
> virtual memory (kbytes) unlimited
>
> thanks... I thought of that as well.
>
> - Greg
>
> -----Original Message-----
> From: The Hermit Hacker [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 11, 2000 4:32 PM
> To: Gregory Krasnow
> Cc: [EMAIL PROTECTED]
> Subject: Re: [GENERAL] backend running out of memory in v7.0
>
>
> On Thu, 11 May 2000, Gregory Krasnow wrote:
>
> > I know that there were some issues with many AND/OR joins in
> > PostgreSQL 6.5 which caused the backend process to run out of memory.
> > I am still having some similar issues in PostgreSQL 7.0. I was
> > wondering if there some recommended configurations (i.e. amount of RAM
> > on the machine, size of swap partition, buffers settings for backend
> > process) which I could use to help with my problems. If I cannot
> > create complex AND/OR queries, I cannot use PostgreSQL for my needs
> > and will have to turn back to using MySQL which has no problems with
> > the same queries.
>
> Might be even more simple then that ... I've seen the problem here, and
> each time its cause I ... ummm ... forgot to raise the limits for the
> pgsql user :( doing a 'unlimit' before starting postmaster fixes my
> problem each time ...
>
> Marc G. Fournier ICQ#7615664 IRC Nick:
> Scrappy
> Systems Administrator @ hub.org
> primary: [EMAIL PROTECTED] secondary:
> scrappy@{freebsd|postgresql}.org
>
Marc G. Fournier ICQ#7615664 IRC Nick:
Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary:
scrappy@{freebsd|postgresql}.org
