| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Standby server won't start |
| Date: | 2014-03-21 08:10:31 |
| Message-ID: | 20140321.171031.1373661330389978103.t-ishii@sraoss.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I changed primary servers max_connections from 100 to 4 for just a
testing purpose. Now standby server won't start and complains:
hot standby is not possible because max_connections = 4 is a lower setting than on the master server (its value was 100)
My guess is this is because standby's pg_control file contains
previous primary setting (max_connections = 100). Is there any way to
start the standby server without re-creating pg_control (which implies
getting base backup again)? If not, there should be some way to allow
to start standby server without getting base backup...
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | MauMau | 2014-03-21 08:58:19 | Re: [bug fix] PostgreSQL fails to start on Windows if it crashes after tablespace creation |
| Previous Message | Dilip kumar | 2014-03-21 07:48:56 | Re: TODO : Allow parallel cores to be used by vacuumdb [ WIP ] |