| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | josh(at)agliodbs(dot)com |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: unite recovery.conf and postgresql.conf |
| Date: | 2011-09-24 15:05:41 |
| Message-ID: | 20110925.000541.123161884205403406.t-ishii@sraoss.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> I'm not sure what you mean by "not deal with" but part of pgpool-II's
>> functionality assumes that we can easily generate recovery.conf. If
>> reconf.conf is integrated into postgresql.conf, we need to edit
>> postgresql.conf, which is a little bit harder than generating
>> recovery.conf, I think.
>
> Oh? Clearly I've been abusing pgPool2 then. Where's the code that
> generates that?
pgpool-II itself does not generate the file but scripts for pgpool-II
are generating the file as stated in documentation comimg with
pgpool-II.
--
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 | Magnus Hagander | 2011-09-24 15:08:17 | posix_fadvsise in base backups |
| Previous Message | Bruce Momjian | 2011-09-24 14:49:54 | Re: Range Types - symmetric |