Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Notification when freespaces empty
- From: ITAGAKI Takahiro <itagaki(dot)takahiro(at)lab(dot)ntt(dot)co(dot)jp>
- To: Simon Riggs <simon(at)2ndquadrant(dot)com>
- Cc: pgsql-hackers(at)postgresql(dot)org
- Subject: Re: Notification when freespaces empty
- Date: Tue, 24 May 2005 17:23:26 +0900
- Message-id: <20050524165249.3AB4.ITAGAKI.TAKAHIRO@lab.ntt.co.jp> <text/plain>
Simon Riggs <simon(at)2ndquadrant(dot)com> wrote: > > Furthermore, this patch detaches empty fsmpages then. > Does that do anything useful though? > I thought we don't reallocate until VACUUM time, whereupon we identify > any empty slots and reuse them. Who cares whether we deallocate earlier? Yes, we cannot reuse them until next VACUUM. But I think it is a problem that FSMs keep being scanned after they are almost empty. In such a case, most stored pages are touched whenever new pages are requested. I intended to cut FSMs earlier in order to omit the scans. --- ITAGAKI Takahiro NTT Cyber Space Laboratories
- References:
- Notification when freespaces empty
- From: ITAGAKI Takahiro
- Re: Notification when freespaces empty
- From: Simon Riggs
- Notification when freespaces empty
- Prev by Date: Re: Speeding up the Postgres lexer
- Next by Date: Re: INSTEAD OF trigger on VIEWs
- Previous by thread: Re: Notification when freespaces empty
- Next by thread: Re: Notification when freespaces empty
- Indexes: