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

Re: crash-safe visibility map, take three

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>, "Bruce Momjian" <bruce(at)momjian(dot)us>
Cc: "Robert Haas" <robertmhaas(at)gmail(dot)com>, <pgsql-hackers(at)postgresql(dot)org>,"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: crash-safe visibility map, take three
Date: 2010-12-01 14:57:51
Message-ID: 4CF60E0F0200002500037FEE@gw.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-hackers
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2010-12-01 14:59:17
Subject: Re: Proposal: First step towards Intelligent, integrateddatabase
Previous:From: Mario WeilguniDate: 2010-12-01 14:51:35
Subject: Re: DELETE with LIMIT (or my first hack)

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