| From: | Decibel! <decibel(at)decibel(dot)org> | 
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> | 
| Cc: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> | 
| Subject: | Re: New FSM patch | 
| Date: | 2008-09-18 02:00:32 | 
| Message-ID: | B7895926-718C-49F3-902C-3C2277D66F99@decibel.org | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
On Sep 17, 2008, at 9:30 AM, Heikki Linnakangas wrote:
> I think we'd still need to WAL log operations that decrease the  
> amount of free space on page. Otherwise, after we have partial  
> vacuum, we might never revisit a page, and update the FSM, even  
> though there's usable space on the page, leaving the space  
> forgotten forever.
ISTM that it would be better to deal with such corner cases via  
periodic non-partial vacuums, done by something like autovac, and  
probably done with an ever higher-than-normal vacuum_cost_delay  
setting so as to minimize performance. That's likely a lot less  
wasteful than further compounding lock contention for the WAL. Even  
if it does result in more overall IO, you have to trade a *lot* of IO  
to balance out the impact of lock contention.
-- 
Decibel!, aka Jim C. Nasby, Database Architect  decibel(at)decibel(dot)org
Give your computer some brain candy! www.distributed.net Team #1828
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ITAGAKI Takahiro | 2008-09-18 02:32:31 | 0x1A in control file on Windows | 
| Previous Message | Alvaro Herrera | 2008-09-17 23:46:17 | Re: optimizing CleanupTempFiles |