Re: How do you change the size of the WAL files?

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Ron Somaraju <RSomaraju(at)masergy(dot)com>
Cc: David Johnston <polobo(at)yahoo(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: How do you change the size of the WAL files?
Date: 2012-01-10 17:38:00
Message-ID: CAOR=d=0D5MRnJfQJoOtrk3XBSAaJsg1Ua3ve9EotBc_07Cx7dQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Jan 10, 2012 at 8:56 AM, Ron Somaraju <RSomaraju(at)masergy(dot)com> wrote:
> David, thanks for the response. I appreciate it. I hope the community understands the benefit of providing the functionality to be able to dynamically increase WAL size without having to re-init the cluster (which I think is the work around). In this information age an OLTP or OLAP database with an average size of 1to 3Tb size is not uncommon. With that in view an active database could generate hundreds of 16Mb files within a very short time. In my case we are moving a large active database from Oracle to Postgresql. In Postgres I am seeing an average of 15 to 23 WAL 16Mb files every minute.

While I'd love to see a test of how things work with 64M WAL files,
I'd worry about how well tested that particular code path was to use
in production. OTOH small incremental changes are often the best to
test with.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Michael P. Soulier 2012-01-10 18:48:58 memory leak
Previous Message Tom Lane 2012-01-10 16:42:09 Re: string = any()