| From: | Luca Ferrari <fluca1978(at)infinito(dot)it> |
|---|---|
| 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 09:01:42 |
| Message-ID: | CAKoxK+4q4AerC0etsHg9Evuy__wSBWuth_tK0fLwpz7BkQb=XA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Jan 9, 2014 at 11:42 AM, Willy-Bas Loos <willybas(at)gmail(dot)com> wrote:
> 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?
Interesting. pg_dump works in a transactional model, but it should be
on read only. Is it possible you have dirty pages that are made
persistent due to pg_dump? Or could it be a vacuum process or
something related to freezing the tuples?
Luca
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rémi Cura | 2014-01-10 09:10:28 | excution time for plpgsql function and subfunction |
| Previous Message | ygnhzeus | 2014-01-10 09:00:29 | How to specify/mock the statistic data of tables in PostgreSQL |