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
pa
: 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
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: [GE
ND (cms_users.usr_id= cms_opt_in.usr_id)
AND usr_glob_sub=1
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 11, 2000 6:21 PM
To: Bruce Momjian
Cc: Gregory Krasnow; [EMAIL PROTECTED]
Subject: Re: [GENERAL] backend running out of memory in v7.0
Bruce Momjian <
thanks.. I will try creating that function. :)
- Greg
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 12, 2000 8:24 AM
To: Gregory Krasnow
Cc: Bruce Momjian; [EMAIL PROTECTED]
Subject: Re: [GENERAL] backend running out of memory in v7.0
Gregory Krasnow
one more thing... what does this error mean?
psql:tst3.sql:21: ERROR: plpgsql: cache lookup from pg_proc failed
I keep seeing the following whenever there is a new client connection to the
database:
Error semaphore semaphore not equal 0
anyone know what this means? Thanks.
- Greg
