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

From Robert Haas
Subject Re: BUG #7521: Cannot disable WAL log while using pg_dump
Date
Msg-id CA+TgmoY7fam6-V+gH-t3yffZEGhB=SPoXNp6O8XP_kHdAKVBag@mail.gmail.com
Whole thread Raw
In response to Re: BUG #7521: Cannot disable WAL log while using pg_dump  (Heikki Linnakangas <hlinnaka@iki.fi>)
List pgsql-bugs
On Thu, Sep 6, 2012 at 4:08 PM, Heikki Linnakangas <hlinnaka@iki.fi> wrote:
> On 06.09.2012 13:07, Robert Haas wrote:
>>>> pg_dump doesn't modify any data, so I don't see how it could be
>>>> causing WAL logs to get generated.
>>>
>>> Doesn't hint-bit setting cause WAL traffic these days?
>>
>> I sure as heck don't think so.
>
> It does not. HOT page pruning does, however. It could be that..

True, but wouldn't you have to be fantastically unlucky for that to
amount to anything material?  I mean, what are the chances of that
happening on more than a very small percentage of blocks?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-bugs by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: BUG #7521: Cannot disable WAL log while using pg_dump
Next
From: Tom Lane
Date:
Subject: Re: BUG #7521: Cannot disable WAL log while using pg_dump