Re: [HACKERS] Buglist

From: Manfred Koizar <mkoi-pg(at)aon(dot)at>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jan Wieck <JanWieck(at)Yahoo(dot)com>, Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in>, pgsql-general(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] Buglist
Date: 2003-08-22 16:20:26
Message-ID: 1hdckvggldmn79t3g3oj9o3mr96lcolkka@4ax.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On Fri, 22 Aug 2003 10:45:50 -0400, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
wrote:
>One big question mark in my mind about these "partial vacuum"
>proposals is whether they'd still allow adequate FSM information to be
>maintained. If VACUUM isn't looking at most of the pages, there's no
>very good way to acquire info about where there's free space.

VACUUM has accurate information about the pages it just visited. Free
space information for pages not touched by VACUUM is still in the FSM,
unless free space on a page is too low to be interesting. VACUUM has
to merge these two lists and throw away entries with little free space
if running out of room.

Thus we might end up with new almost full pages in the FSM while there
are pages with more free space lying around that a previous VACUUM
failed to register because there was more free space at that time.

Considering that
. FSM is lossy per definitionem
. we are targeting at relations with large passive areas
. decent VACUUM shall not replace lazy VACUUM
I see no problem here.

Future advice could be: "VACCUM DECENT every hour, VACUUM daily,
VACUUM FULL once a year" where the first two could be scheduled by
autovacuum ...

Servus
Manfred

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Greg Stark 2003-08-22 16:20:40 Re: Collation rules and multi-lingual databases
Previous Message Dennis Gearon 2003-08-22 16:19:03 Re: Collation rules and multi-lingual databases

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-08-22 16:21:09 Re: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12
Previous Message Jan Wieck 2003-08-22 16:18:02 Re: [HACKERS] Buglist