| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: FPI |
| Date: | 2011-01-28 15:13:01 |
| Message-ID: | 19140.1296227581@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> I was thinking about full-page writes again tonight. I'm still
> wondering about the feasibility of getting rid of full-page writes for
> certain operations. We can do this, I think, in any case where we can
> convince ourselves that if the original operation, or a redo of the
> original operation, leaves behind a torn page, a subsequent redo will
> still DTRT.
> I think that both tuple freezing (XLOG_HEAP2_FREEZE) and heap
> deletions (XLOG_HEAP_DELETE) are close to having this property.
Say what? A heap deletion compacts the page --- it will certainly fail
badly on torn-page.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2011-01-28 15:23:01 | Re: mingw64 |
| Previous Message | Boszormenyi Zoltan | 2011-01-28 13:56:44 | Re: make -j2 error in ecpg/pgtypeslib in current GIT |