Re: crash-safe visibility map, take three - Mailing list pgsql-hackers

From Robert Haas
Subject Re: crash-safe visibility map, take three
Date
Msg-id AANLkTikU5VtO1XW5-=gLvJA=cX66CsMo42AKVWYMGHZW@mail.gmail.com
Whole thread Raw
In response to Re: crash-safe visibility map, take three  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
On Wed, Dec 1, 2010 at 9:57 AM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
> Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> wrote:
>
>> it would be annoying to have to checkpoint after a data load
>
> Heck, in my world it's currently pretty much a necessity to run
> VACUUM FREEZE ANALYZE on a table after a data load before it's
> reasonable to expose the table to production use.  It would hardly
> be an inconvenience to also run a CHECKPOINT.

The goal here is to make that better, not worse!

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: crash-safe visibility map, take three
Next
From: Florian Pflug
Date:
Subject: Re: FK's to refer to rows in inheritance child