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

From: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>
To: Gezeala M(dot) Bacuño II <gezeala(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Boy de Laat <boy(at)atsc(dot)nl>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #7521: Cannot disable WAL log while using pg_dump
Date: 2012-09-07 13:29:06
Message-ID: CABOikdN-jGtEg=LVUTL8Jxjs0xqgHCPLASKEZ3NmgaRTC+xNXw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Fri, Sep 7, 2012 at 12:15 PM, Gezeala M. Bacuño II <gezeala(at)gmail(dot)com>wrote:

> The instance is cloned solely for
> backup purposes with zero modifications and autovacuum disabled.
>

For your restricted use case, it might be worthwhile to
turn full_page_writes OFF before starting the server. That should
definitely reduce a lot of WAL volume.

Thanks,
Pavan

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Pavan Deolasee 2012-09-07 18:29:50 Re: [BUGS] BUG #7521: Cannot disable WAL log while using pg_dump
Previous Message Pavan Deolasee 2012-09-07 09:19:32 Re: BUG #7521: Cannot disable WAL log while using pg_dump

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2012-09-07 13:57:11 Re: Draft release notes complete
Previous Message Amit kapila 2012-09-07 13:14:56 Re: [WIP PATCH] for Performance Improvement in Buffer Management