Re: BUG #7521: Cannot disable WAL log while using pg_dump

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: hlinnaka(at)iki(dot)fi
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, boy(at)atsc(dot)nl, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #7521: Cannot disable WAL log while using pg_dump
Date: 2012-09-06 20:10:15
Message-ID: CA+TgmoY7fam6-V+gH-t3yffZEGhB=SPoXNp6O8XP_kHdAKVBag@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Thu, Sep 6, 2012 at 4:08 PM, Heikki Linnakangas <hlinnaka(at)iki(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2012-09-06 20:23:07 Re: BUG #7521: Cannot disable WAL log while using pg_dump
Previous Message Heikki Linnakangas 2012-09-06 20:08:39 Re: BUG #7521: Cannot disable WAL log while using pg_dump

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-09-06 20:23:07 Re: BUG #7521: Cannot disable WAL log while using pg_dump
Previous Message Heikki Linnakangas 2012-09-06 20:08:39 Re: BUG #7521: Cannot disable WAL log while using pg_dump