Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: CREATE TABLE, load and freezing
- From: Florian Pflug <fgp(dot)phlo(dot)org(at)gmail(dot)com>
- To: ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
- Cc: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>
- Subject: Re: CREATE TABLE, load and freezing
- Date: Thu, 28 Feb 2008 14:42:49 +0100
ITAGAKI Takahiro wrote:
Without this, very large read-only tables would require one round of complete freezing if there are lot of transactional activities in the other parts of the database. And when that happens, it would generate lots of unnecessary IOs on these large tables.To make things worse, the freezing day comes at once because the first restore is done in a single or near transactions; The wraparound timings of many tables are aligned at the same time. Freezing copy will be the solution.
Hm.. Couldn't we eliminate that particular concern easily by adding some randomness to the freeze_age?
regards, Florian Pflug
- References:
- CREATE TABLE, load and freezing
- From: Pavan Deolasee
- Re: CREATE TABLE, load and freezing
- From: ITAGAKI Takahiro
- CREATE TABLE, load and freezing
- Prev by Date: Re: Buildfarm member gypsy_moth seems not to like alignment patch
- Next by Date: Re: Silly Newbie question
- Previous by thread: Re: CREATE TABLE, load and freezing
- Next by thread: Re: CREATE TABLE, load and freezing
- Indexes: