pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Visibility map, partial vacuums
Date: Wed, 26 Nov 2008 17:44:24 +0200
Message-ID: <492D6ED8.5070105@enterprisedb.com> (raw)
In-Reply-To: <7144.1227707910@sss.pgh.pa.us>
References: <4905AE17.7090305@enterprisedb.com>
	<491D376B.9000608@enterprisedb.com>
	<491D7F52.6070908@enterprisedb.com>
	<4925664C.3090605@enterprisedb.com>
	<26361.1227467112@sss.pgh.pa.us>
	<492A6032.6080000@enterprisedb.com>
	<18086.1227537479@sss.pgh.pa.us>
	<492D4460.1000809@enterprisedb.com>
	<5856.1227705135@sss.pgh.pa.us>
	<492D4FF0.2000606@enterprisedb.com>
	<7144.1227707910@sss.pgh.pa.us>

Tom Lane wrote:
> Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
>> Tom Lane wrote:
>>> Well, considering how seldom new pages will be added to the visibility
>>> map, it seems to me we could afford to send out a relcache inval event
>>> when that happens.  Then rd_vm_nblocks_cache could be treated as
>>> trustworthy.
> 
>> A relcache invalidation sounds awfully heavy-weight.
> 
> It really isn't.

Okay, then. I'll use relcache invalidation for both the FSM and 
visibility map.

-- 
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com



view thread (53+ messages)  latest in thread

Message-ID: <492D6ED8.5070105@enterprisedb.com>
Permalink:  ../492D6ED8.5070105@enterprisedb.com/
Also on:    postgresql.org/message-id/492D6ED8.5070105@enterprisedb.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: heikki.linnakangas@enterprisedb.com, tgl@sss.pgh.pa.us
  Subject: Re: Visibility map, partial vacuums
  In-Reply-To: <492D6ED8.5070105@enterprisedb.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox