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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: hlinnaka(at)iki(dot)fi, 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 21:06:47
Message-ID: CA+Tgmobjs7FOJ11fB2JRtRs+M+OF3thwAiyjcK=rmE4xcjz+dw@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:23 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Heikki Linnakangas <hlinnaka(at)iki(dot)fi> writes:
>> On 06.09.2012 13:07, Robert Haas wrote:
>>> On Thu, Sep 6, 2012 at 3:55 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>>> 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..
>
> 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.

But that only happens in vacuum, which pg_dump does not do.

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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2012-09-06 21:07:14 Re: BUG #7521: Cannot disable WAL log while using pg_dump
Previous Message Tom Lane 2012-09-06 20:58:11 Re: BUG #4958: Stats collector hung on WaitForMultipleObjectsEx while attempting to recv a datagram

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2012-09-06 21:07:14 Re: BUG #7521: Cannot disable WAL log while using pg_dump
Previous Message Robert Haas 2012-09-06 21:03:02 Re: Reduce the time to know trigger_file's existence