Re: wal-size limited to 16MB - Performance issue for subsequent backup

From: jesper(at)krogh(dot)cc
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: jesper(at)krogh(dot)cc, "Pg Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: wal-size limited to 16MB - Performance issue for subsequent backup
Date: 2014-10-20 19:27:39
Message-ID: 1fcb1c980fa7418199054a98ec00c566.squirrel@shrek.krogh.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> jesper(at)krogh(dot)cc writes:
>> Thread here around the same topic:
>> http://postgresql.1045698.n5.nabble.com/How-do-you-change-the-size-of-the-WAL-files-td3425516.html
>> But not a warm welcoming workaround.
>
> configure --with-wal-segsize=something ?

Yes, but there are good reasons not to go down that route. One is that:

1) It looks like I'am going to be the only one, beware of the dragons.
2) It requires apparently a re-initdb, thus dump/restore of 4.5TB of data

The latter can absolutely be done by scheduling downtime, but the former
would compromise any level of good practice around our DB-operations.

Jesper

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2014-10-20 19:35:08 Re: wal-size limited to 16MB - Performance issue for subsequent backup
Previous Message ktm@rice.edu 2014-10-20 19:27:21 Re: wal-size limited to 16MB - Performance issue for subsequent backup