Skip site navigation (1) Skip section navigation (2)

Re: Not HOT enough

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Not HOT enough
Date: 2011-11-23 16:14:04
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Wed, Nov 23, 2011 at 3:20 PM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
> Excerpts from Robert Haas's message of mié nov 23 12:15:55 -0300 2011:
>> > And it effects shared catalogs only, which are all low traffic anyway.
>> I think "low traffic" is the key point.  I understand that you're not
>> changing the VACUUM behavior, but you are making heap_page_prune_opt()
>> not do anything when a shared catalog is involved.  That would be
>> unacceptable if we expected shared catalogs to be updated frequently,
>> either now or in the future, but I guess we don't expect that.
> Maybe not pg_database or pg_tablespace and such, but I'm not so sure
> about pg_shdepend.  (Do we record pg_shdepend entries for temp tables?)

Normal catalog access does not use HOT and never has.

If catalogs need VACUUMing then autovacuum takes care of it.

If we're saying that isn't enough and we actually depend on the
occasional user inspecting the catalog then we are already hosed.

 Simon Riggs         
 PostgreSQL Development, 24x7 Support, Training & Services

In response to


pgsql-hackers by date

Next:From: Mika ElorantaDate: 2011-11-23 16:24:43
Subject: PL/Python SQL error code pass-through
Previous:From: Merlin MoncureDate: 2011-11-23 16:07:18
Subject: Re: [JDBC] Optimize postgres protocol for fixed size arrays

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group