Re: wal-size limited to 16MB - Performance issue for subsequent backup - Mailing list pgsql-hackers

From jesper@krogh.cc
Subject Re: wal-size limited to 16MB - Performance issue for subsequent backup
Date
Msg-id 1fcb1c980fa7418199054a98ec00c566.squirrel@shrek.krogh.cc
Whole thread Raw
In response to Re: wal-size limited to 16MB - Performance issue for subsequent backup  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: wal-size limited to 16MB - Performance issue for subsequent backup
List pgsql-hackers
> jesper@krogh.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





pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Superuser connect during smart shutdown
Next
From: "ktm@rice.edu"
Date:
Subject: Re: wal-size limited to 16MB - Performance issue for subsequent backup