Re: getting rid of freezing

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: getting rid of freezing
Date: 2013-05-29 17:11:13
Message-ID: 1369847473.9884.7.camel@jdavis-laptop
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 2013-05-28 at 19:51 -0400, Robert Haas wrote:
> > If we just wanted to reduce read cost, why not just take a simpler
> > approach and give the visibility map a "isfrozen" bit? Then we'd know
> > which pages didn't need rescanning without nearly as much complexity.
>
> That would break pg_upgrade, which would have to remove visibility map
> forks when upgrading. More importantly, it would require another
> round of complex changes to the write-ahead logging in this area.
> It's not obvious to me that we'd end up ahead of where we are today,
> although perhaps I am a pessimist.

If we removed PD_ALL_VISIBLE, then this would be very simple, right? We
would just follow normal logging rules for setting the visible or frozen
bit.

Regards,
Jeff Davis

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2013-05-29 17:18:35 Re: getting rid of freezing
Previous Message Jeff Davis 2013-05-29 16:53:24 Re: visibilitymap_set and checksums