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

From Kevin Grittner
Subject Re: crash-safe visibility map, take three
Date
Msg-id 4CF60E0F0200002500037FEE@gw.wicourts.gov
Whole thread Raw
In response to Re: crash-safe visibility map, take three  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: crash-safe visibility map, take three  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
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.
-Kevin


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: KNNGIST next step: adjusting indexAM API
Next
From: Mario Weilguni
Date:
Subject: Re: DELETE with LIMIT (or my first hack)