From: | Hannu Krosing <hannu(at)skype(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: Is full_page_writes=off safe in conjunction with |
Date: | 2006-04-15 21:10:14 |
Message-ID: | 1145135414.6098.7.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Ühel kenal päeval, L, 2006-04-15 kell 11:49, kirjutas Tom Lane:
> Hannu Krosing <hannu(at)skype(dot)net> writes:
> > If I'm desperate enough to get the 2x reduction of WAL writes, I may
> > even write my own backup solution.
>
> Given Florian's concern, sounds like you might have to write your own
> kernel too. In which case, generating a variant build of Postgres
> that allows full_page_writes to be disabled is certainly not beyond
> your powers. But for the ordinary mortal DBA, I think this combination
> is just too unsafe to even consider.
I guess that writing our own pg_tar, which cooperates with postgres
backends to get full pages, is still in the realm of possible things,
even on kernels which dont guarantee atomic visibility of write() calls.
But until such is included in the distribution it is a good idea indeed
to disable full_page_writes=off when doing PITR.
--------------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2006-04-15 23:02:54 | Re: Google SoC--Idea Request |
Previous Message | Dave Page | 2006-04-15 20:24:48 | Re: Google SoC--Idea Request |