[Pgpool-general] failback setup problem

[Tatsuo Ishii]

>> >> I'm not sure what you are trying to do here. If "backup" means it was
>> >> created by pg_dump_all, I don't think your approach works. Streaming
>> >> replication requires a base backup(binary backup) which is managed by
>> >> pg_start_backup/pg_stop_backup.
>> >>
>> >
>> > Yes of course I have a backup created as described in
>> >
>> http://www.postgresql.org/docs/9.0/static/continuous-archiving.html#BACKUP-BASE-BACKUP

If you keep wal archives along with the base backup, then it should be
possible to recover primary PostgreSQL from them of course. Question
is, how to recover standbys. In my understanding you need to recreate
them from the recovered primary anyway and it will require *new* base
backup.

>> > My question is, what happens if both server failed somehow? Can I still
>> use
>> > pgpoolAdmin to recover a database server?
>>
>> No, pgpoolAdmin cannot recover a database server in this situation.
>> You have to recover the database manualy.
>>
> Yes. I thought that of course.
> So my question was, if you leave the whole restore process up to one called
> recovery script - including optional checkpointing etc. pgpool would be more
> flexible and simplier in terms of supporting different recovery procedures.

Good question. I will inspect current code if your idea is possible
while updating docs.

> By he way - where does pgpool actually store the information about
> attached/detached servers?

On shared memory.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp