| From: | Hannu Krosing <hannu(at)skype(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Marko Kreen <markokr(at)gmail(dot)com>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Is full_page_writes=off safe in conjunction with |
| Date: | 2006-04-16 19:46:46 |
| Message-ID: | 1145216807.3699.2.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Ühel kenal päeval, P, 2006-04-16 kell 11:31, kirjutas Tom Lane:
> "Marko Kreen" <markokr(at)gmail(dot)com> writes:
> > So we should probably document that rsync is only working solution.
>
> No, we're just turning off the variable. One experiment on one version
> of rsync doesn't prove it's "safe", even if there weren't the kernel-
> behavior issue to consider.
But if we do need to consider the kernel-level behaviour mentioned, then
the whole PITR thing becomes an impossibility. Consider the case when we
get a torn page during the initial copy with tar/cpio/rsync/whatever,
and no WAL record updates it.
In that case we will just have a torn page in backup with no way to fix
it.
-------------
Hannu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-04-16 20:24:57 | Re: Is full_page_writes=off safe in conjunction with |
| Previous Message | Gevik Babakhani | 2006-04-16 18:34:10 | Re: Regrading TODO item alerting pg_hba.conf from SQL |