[EMAIL PROTECTED] writes:
>> It sounds like you forgot to restart the postmaster after changing
>> postgresql.conf. This is one of the parameters that is frozen at
>> server start ...
> No, I did restart the postmaster. Actually more than once.
In that case, maybe you edited the wrong copy of postgresql.conf?
Try checking "SHOW max_connections" to verify what the postmaster
thinks the value is.
> I do not have to restart the server after changing kernel parameters
> with sysctl, do I?
I don't think kernel limits would lead to "too many clients" --- you'd
be getting different sorts of failures if the problem were in that area.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
