Re: [HACKERS] Buglist

From: Manfred Koizar <mkoi-pg(at)aon(dot)at>
To: Jan Wieck <JanWieck(at)Yahoo(dot)com>
Cc: 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:54:05
Message-ID: 8uhckvg4cfh4kk1oq9j755dd1qu6r7t0kn@4ax.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On Fri, 22 Aug 2003 12:18:02 -0400, Jan Wieck <JanWieck(at)Yahoo(dot)com>
wrote:
>Okay, my proposal would be to have a VACUUM mode where it tells the
>buffer manager to only return a page if it is already in memory

But how can it know? Yes, we know exactly what we have in PG shared
buffers. OTOH we keep telling people that they should configure
moderate values for shared_buffers because the OS is better at
caching. Your CACHEONLY VACUUM wouldn't catch those pages that are in
the OS cache but not in the shared buffers, although they are
retrievable at almost the same low cost.

We should not try to avoid _any_ physical disk access. It's good
enough to avoid useless reads. Hence my proposal for a reclaimable
space list ...

Servus
Manfred

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2003-08-22 16:56:01 Re: [HACKERS] Buglist
Previous Message Jan Wieck 2003-08-22 16:49:33 Re: Single-file DBs WAS: Need concrete "Why Postgres

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-08-22 16:56:01 Re: [HACKERS] Buglist
Previous Message Jan Wieck 2003-08-22 16:49:33 Re: Single-file DBs WAS: Need concrete "Why Postgres