Torsten Förtsch wrote:
> Now, I have a database with very low write activity. Archive_command is
> called about once per hour to
> archive one segment. When the database was moved to PG 9.5, it was initially
> configured with insanely
> high settings for max_wal_size, min_wal_size and wal_keep_se
On Tue, Nov 22, 2016 at 10:34 PM, Adrian Klaver
wrote:
> On 11/22/2016 12:51 PM, Torsten Förtsch wrote:
>
>>
>> Now, I have a database with very low write activity. Archive_command is
>> called about once per hour to archive one segment. When the database was
>> moved to PG 9.5, it was initially
On 11/22/2016 12:51 PM, Torsten Förtsch wrote:
Hi,
I am a bit confused about min_wal_size and max_wal_size. Previously,
there was this formula to estimate the max number of WAL segment files
in pg_xlog/
(https://www.postgresql.org/docs/9.4/static/wal-configuration.html):
(2 + checkpoint_compl
