From: | John R Pierce <pierce(at)hogranch(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Tunning Server 9.1. |
Date: | 2016-08-05 00:44:07 |
Message-ID: | a43ba482-8783-1e93-421b-4a9e4856d111@hogranch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 8/4/2016 2:02 PM, Periko Support wrote:
> I read some sites on google that it was related to this settings.
> Can u share your experience on this logs?
what you said earlier has nothing to do with what you're saying now.
original:
> I have server that hras increase users and need to increase
> max_connections from default value.
>
> Current value = 100
> New Value = 200
>
> This send me a message about shared_memory need to lower the value
> which default settings = 24MB.
then you said...
> This was my message:
>
> PDT FATAL: remaining connection slots are reserved for
> non-replication superuser connections
>
> Reading about, some points to max_connections because we have increase
> users on the network, I tought has sense.
I don't get how you got from that first to that second. "remaining
connections are reserved..." happens when more than max_connections
clients connect to the server. this has nothing to do with shared
memory.
now, if after increasing max_connections you got ANOTHER message about
shared memory, THATS the error we need to see.
--
john r pierce, recycling bits in santa cruz
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2016-08-05 08:16:36 | Re: Uber migrated from Postgres to MySQL |
Previous Message | Ian Barwick | 2016-08-04 22:54:59 | Re: Streaming Replica Master-Salve Config. |