Currently pg_rewind copies all files including postgresql.conf. It would be nice if pg_rewind has an option to not copy postgresql.conf. I sometimes create multiple PostgreSQL database clusters with different port number which postmaster is listening on for a testing purpose. So existing postgresql.conf on the target cluster being overwritten by pg_rewind is annoying. I believe there are some use cases where different port numbers are used among PostgreSQL database clusters in the real world.
Comments? -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese:http://www.sraoss.co.jp
