Re: Online enabling of checksums - Mailing list pgsql-hackers

From Sergei Kornilov
Subject Re: Online enabling of checksums
Date
Msg-id 3526971530019277@web36j.yandex.ru
Whole thread Raw
In response to Re: Online enabling of checksums  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Online enabling of checksums
List pgsql-hackers
Hello

I tried build this patch and got error during make docs
> postgres.sgml:19626: element xref: validity error : IDREF attribute linkend references an unknown ID
"runtime-checksumhelper-cost-limit"
> postgres.sgml:19625: element xref: validity error : IDREF attribute linkend references an unknown ID
"runtime-checksumhelper-cost-delay"

Both new GUC checksumhelper_cost_delay and checksumhelper_cost_limit mentioned in postgresql.conf with special value -1
(-1to use vacuum_cost_limit), but this value was not mentioned in docs. I noticed that the code and documentation
describedifferent defaults.
 
Also i found one "<literal>in progress</literal>" in pg_enable_data_checksums() description. In other places status is
called"inprogress" (without space).
 

>    VacuumPageHit = 0;
>    VacuumPageMiss = 0;
>    VacuumPageDirty = 0;
Hm, why these settings are set to 0 in checksumhelper process?

> /*
> * Force a checkpoint to get everything out to disk. XXX: this should
> * probably not be an IMMEDIATE checkpoint, but leave it there for now for
> * testing
> */
> RequestCheckpoint(CHECKPOINT_FORCE | CHECKPOINT_WAIT | CHECKPOINT_IMMEDIATE);
We need not forget that.

regards, Sergei


pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: [HACKERS] GUC for cleanup indexes threshold.
Next
From: Ashutosh Bapat
Date:
Subject: Re: Thinko/typo in ExecSimpleRelationInsert