From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
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:08:39 |
Message-ID: | 504902C7.9030903@iki.fi |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
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:
>> Robert Haas<robertmhaas(at)gmail(dot)com> writes:
>>> On Wed, Sep 5, 2012 at 9:57 AM,<boy(at)atsc(dot)nl> wrote:
>>>> So it would be nice if there is an option to disable WAL logging while
>>>> running pg_dump.
>>
>>> 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..
- Heikki
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2012-09-06 20:10:15 | Re: BUG #7521: Cannot disable WAL log while using pg_dump |
Previous Message | Robert Haas | 2012-09-06 20:07:27 | Re: BUG #7521: Cannot disable WAL log while using pg_dump |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2012-09-06 20:10:15 | Re: BUG #7521: Cannot disable WAL log while using pg_dump |
Previous Message | Robert Haas | 2012-09-06 20:07:27 | Re: BUG #7521: Cannot disable WAL log while using pg_dump |