Thank you, Tatsuo and Tomasz, I appreciate your input, and the caveat about the status. Just to satisfy my curiosity, would running pcp_attach_node after startup be another acceptable solution to the status problem?
Thank you, AW On Wed, Jun 15, 2011 at 7:24 PM, Tatsuo Ishii <[email protected]> wrote: >>>> What should be the course of action if I run multiple pgpool-II >>>> instances, and I need to recover a database? For example, let my >>>> environment consist of multiple, redundant application servers, each >>>> with its own pgpool. Attached to each pgpool is the same set of >>>> Postgres clusters, of course. My guess would be to perform the >>>> following steps: >>>> >>>> 1) Shut down all pgpool/app server pairs except for one (thus, for a >>>> small period of time, all connections will go through the one remaning >>>> pgpool/app server - this is fine for me) >>>> 2) Perform online recovery on the remaining pgpool >>>> 3) Start up all the previously-shutdown pgpools/app servers. >>> >>> Yes, these are exactly the steps you need. >> >> Note that pgpool will have its status file, where it will remember the >> state of the nodes (i.e. that one of the nodes is in state 3 - >> kicked). >> >> Prior to starting pgpool, you will need to remove this file. > > Or use -D option. > -- > Tatsuo Ishii > SRA OSS, Inc. Japan > English: http://www.sraoss.co.jp/index_en.php > Japanese: http://www.sraoss.co.jp > _______________________________________________ Pgpool-general mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-general
