Re: [Postgres-xc-general] Problem with starting datanode slave

[Juned K. <jkh...@gm...>]

Hi Michael,

Why i had to set max_connection value to that much because it was giving me
error like.

FATAL: sorry, too many clients already at /ust/local/...

should i use pgpool to handle that much connection?


On Thu, Apr 17, 2014 at 6:41 AM, Michael Paquier
<mic...@gm...>wrote:

>
>
>
> On Wed, Apr 16, 2014 at 9:53 PM, Juned Khan <jkh...@gm...> wrote:
>
>> Hi All,
>>
>> When i tried to set max_connection value to 1000 it gave me this error
>>
> That's a lot, man! Concurrency between sessions is going to blow up your
> performance.
>
> From the docs i came to know that to use than much connection i have to
>> modify kernel configuration
>>
>> But now i am now trying to set 500 connection instead of 1000 then its
>> giving below error.
>>
>> LOG:  database system was interrupted while in recovery at log time
>> 2014-04-16 09:06:06 WAT
>> HINT:  If this has occurred more than once some data might be corrupted
>> and you might need to choose an earlier recovery target.
>> LOG:  entering standby mode
>> LOG:  restored log file "000000010000000B00000011" from archive
>> FATAL:  hot standby is not possible because max_connections = 500 is a
>> lower setting than on the master server (its value was 1000)
>> LOG:  startup process (PID 16829) exited with exit code 1
>> LOG:  aborting startup due to startup process failure
>>
> Anyone please suggest if any other way is there to fix this like clearing
>> cache or something so it can read correct values.
>>
> Update the master first, then the slave.
> --
> Michael
>