Hello,
[This post is merely to document a fix. A search for '"connection
limit exceeded for non-superusers" site:lists.apple.com' yielded
nothing, so here's a solution for the list archive.]
I'm using WOLips 5165, WO 5.4, and PostgreSQL 8.2.5. I first noticed
this problem when I upgraded to WOLips 5047, and I had hoped going to
5165 today would fix it, but it persisted.
When I generated SQL from an EO model and hit "Execute SQL" from
within Entity Modeler, it regularly failed with the following error:
"FATAL: connection limit exceeded for non-superusers." (I couldn't
determine if there was a pattern to where or when it was failing, but
on some models, it would never execute to completion without this
error.) This can be fixed by increasing 'max_connections' in
postgresql.conf. In my installation, that parameter was originally
30, and I increased it to 50. I had to also _decrease_
'shared_buffers' (from 2400kB to 1200kB), or PostgreSQL would not
start, failing to get a large enough shared memory segment from the
OS. In any case, 1200kB still exceeded the recommended minimum as
noted in that file ("min 128kB or max_connections*16kB").
As an aside, could anyone suggest why this error would occur? Is
Entity Modeler (or more likely, I suppose, the JDBC layer) executing
some of these generated SQL statements concurrently, and hence
exceeding 30 connections?
--
Paul.
w http://logicsquad.net/
h http://paul.hoadley.name/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
