From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Willy-Bas Loos <willybas(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: wal archive peak during pg_dump |
Date: | 2014-01-10 03:12:06 |
Message-ID: | CAB7nPqSBo9dagMveKy7Zikwk+k+EgHvpO28bOCzWOaMvdO9vAw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Jan 9, 2014 at 7:42 PM, Willy-Bas Loos <willybas(at)gmail(dot)com> wrote:
> Hi,
>
> I've set up hot standby slaves for a couple of clusters.
> The wal is cleaned up after use, i don't use it as a backup (yet).
> It seems that the amount of wal peaks shortly after midnight, when pg_dump
> is running.
>
> It doesn't seem logical to me that pg_dump should generate wal, but i
> haven't been able to find a different explanation so far.
> So to make sure, i want to ask you people: can it be that running pg_dump
> creates a lot of wal?
pg_dump does modify any data so it basically does not create any WAL
files. But HOT pruning could, as well as data checksums in this case a
plain SELECT can change some tuple hint bits, which indeed generates
WAL. This reminds me of this thread:
http://www.postgresql.org/message-id/E1T9G6S-0007C4-OV@wrigleys.postgresql.org
It would be interesting to see with xlogdump what is the WAL generated.
Regards,
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-01-10 04:56:35 | Re: postgres.app OS X psql character encoding (utf-8) problem |
Previous Message | Jeff Amiel | 2014-01-09 23:22:25 | Re: Looking for settings/configuration for FASTEST reindex on idle system. |