| From: | Marc Schablewski <ms(at)clickware(dot)de> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Reliability of WAL replication |
| Date: | 2007-10-23 11:58:25 |
| Message-ID: | 471DE1E1.1050701@clickware.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
We had some corrupted data files in the past (missing clog, see
http://archives.postgresql.org/pgsql-bugs/2007-07/msg00124.php) and are
thinking about setting up a warm standby system using WAL replication.
Would an error like the one we had appear in WAL and would it be
replicated too? Or is there some kind of consistency check, that
prevents broken WAL from being restored?
I've already posted this question to the bugs list two weeks ago, but
didn't receive an answer so far. Maybe it was the wrong list for that
kind of question, so we'll give it another try here.
Our customer demands a final statement from us, so we would appreciate a
soon reply ( I know, it's always urgent, isn't it? ;) ).
Regards,
Marc Schablewski
click:ware Informationstechnik GmbH
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rainer Bauer | 2007-10-23 12:02:03 | Re: 8.2.3: Server crashes on Windows using Eclipse/Junit |
| Previous Message | Sergey Konoplev | 2007-10-23 11:53:06 | Re: pg_cancel_backend() does not work with buzz queries |