| From: | Mariel Cherkassky <mariel(dot)cherkassky(at)gmail(dot)com> |
|---|---|
| To: | Sergei Kornilov <sk(at)zsrv(dot)org> |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org, pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Re: checkpoint occurs very often when vacuum full running |
| Date: | 2018-11-15 19:29:49 |
| Message-ID: | CA+t6e1=CNKXUQ1deso+0vB4C4tMtyDPdTbvM19PyqMf+-h3+wg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-performance |
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(at)zsrv(dot)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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron | 2018-11-15 19:57:38 | Re: Can't find a relation in pg_class |
| Previous Message | Sergei Kornilov | 2018-11-15 19:10:42 | Re: checkpoint occurs very often when vacuum full running |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergei Kornilov | 2018-11-15 20:28:40 | Re: checkpoint occurs very often when vacuum full running |
| Previous Message | Sergei Kornilov | 2018-11-15 19:10:42 | Re: checkpoint occurs very often when vacuum full running |