Re: BUG #7521: Cannot disable WAL log while using pg_dump - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #7521: Cannot disable WAL log while using pg_dump
Date
Msg-id 1346964246-sup-5476@alvh.no-ip.org
Whole thread Raw
In response to Re: BUG #7521: Cannot disable WAL log while using pg_dump  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #7521: Cannot disable WAL log while using pg_dump  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-bugs
Excerpts from Tom Lane's message of jue sep 06 17:23:07 -0300 2012:
> Heikki Linnakangas <hlinnaka@iki.fi> writes:
> > On 06.09.2012 13:07, Robert Haas wrote:
> >> On Thu, Sep 6, 2012 at 3:55 PM, Tom Lane<tgl@sss.pgh.pa.us>  wrote:
> >>> Doesn't hint-bit setting cause WAL traffic these days?
>=20
> >> I sure as heck don't think so.
>=20
> > It does not. HOT page pruning does, however. It could be that..
>=20
> Sorry, I was thinking of the freeze case, which is also somewhat
> unlikely --- but if it were happening, it could easily happen on
> most/all pages of a table.

How about secondary effects -- say pg_dump reads a lot of data into
buffers that were previously dirty and those get evicted.  Could page
eviction cause lots of WAL to be emitted?

--=20
=C3=81lvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

pgsql-bugs by date:

Previous
From: Robert Haas
Date:
Subject: Re: BUG #7521: Cannot disable WAL log while using pg_dump
Next
From: Robert Haas
Date:
Subject: Re: BUG #7521: Cannot disable WAL log while using pg_dump