Re: checkpoint occurs very often when vacuum full running - Mailing list pgsql-admin

From Mariel Cherkassky
Subject Re: checkpoint occurs very often when vacuum full running
Date
Msg-id CA+t6e1=CNKXUQ1deso+0vB4C4tMtyDPdTbvM19PyqMf+-h3+wg@mail.gmail.com
Whole thread Raw
In response to Re: checkpoint occurs very often when vacuum full running  (Sergei Kornilov <sk@zsrv.org>)
Responses Re: checkpoint occurs very often when vacuum full running  (Laurenz Albe <laurenz.albe@cybertec.at>)
Re: checkpoint occurs very often when vacuum full running  (Sergei Kornilov <sk@zsrv.org>)
Re: checkpoint occurs very often when vacuum full running  (Sergei Kornilov <sk@zsrv.org>)
List pgsql-admin
First of all thank you for the quick answer. In my case checkpoint happened every one second during the vacuum full so the checkpoint timeout isn't relevant. My guess was that it writes the changes to the wals but I didn't find anything about it in the documentation. Can you share a link that proves it ? I mean basicly the wals should contain the changes, and vacuum full changes the location of the data and not actually the data.

On Thu, Nov 15, 2018, 9:10 PM Sergei Kornilov <sk@zsrv.org wrote:
Hi

Checkpoint can be occurs due timeout (checkpoint_timeout) or due amount of WAL (max_wal_size).
Vacuum full does write all data through WAL and therefore may trigger checkpoint more frequently.

regards, Sergei

pgsql-admin by date:

Previous
From: Sergei Kornilov
Date:
Subject: Re: checkpoint occurs very often when vacuum full running
Next
From: Ron
Date:
Subject: Re: Can't find a relation in pg_class