| From: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Avoiding unnecessary reads in recovery |
| Date: | 2007-04-25 15:02:53 |
| Message-ID: | 462F6D9D.8030503@enterprisedb.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Gregory Stark wrote:
> So in short I think with your patch this piece of code no longer has a role.
> Either your patch kicks in and we never even look at the damaged page at all,
> or we should be treating it as corrupt data and just check zero_damaged_pages
> alone and not do anything special in recovery.
Good point. Adjusted patch attached. I added some comments as well.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| Attachment | Content-Type | Size |
|---|---|---|
| skip-unnecessary-reads-on-recovery-2.patch | text/x-diff | 5.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2007-04-25 15:16:20 | Re: Avoiding unnecessary reads in recovery |
| Previous Message | Andrew Dunstan | 2007-04-25 15:02:49 | Re: ECPG failure on BF member Vaquita (Windows Vista) |