Re: Protecting against unexpected zero-pages: proposal

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: Protecting against unexpected zero-pages: proposal
Date: 2010-11-09 22:03:09
Message-ID: 4CD9C51D.4030301@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 11/9/10 1:50 PM, Robert Haas wrote:
> 5. It would be pretty much impossible to run with autovacuum turned
> off, and in fact you would likely need to make it a good deal more
> aggressive in the specific case of aborted transactions, to mitigate
> problems #1, #3, and #4.

6. This would require us to be more aggressive about VACUUMing old-cold
relations/page, e.g. VACUUM FREEZE. This it would make one of our worst
issues for data warehousing even worse.

What about having this map (and other hintbits) be per-relation? Hmmm.
That wouldn't work for DDL, I suppose ...

--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2010-11-09 22:15:45 Re: Protecting against unexpected zero-pages: proposal
Previous Message David E. Wheeler 2010-11-09 22:00:29 Re: multi-platform, multi-locale regression tests