Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64

From: Cocco Gianfranco <Gianfranco(dot)Cocco(at)eng(dot)it>
To: "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Cc: DBA <DBA(at)italiaonline(dot)it>
Subject: Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64
Date: 2017-06-09 13:55:04
Message-ID: D0D985968D95594199094F94C3F7BCA124415034@ITPMX020.italy.itroot.adnet
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-performance

Hi,
We have a big problem with managing the number of WAL products, during database activity, so I would try to write to you.
With pg_rman utility, we can't save thousands of WAL files every few hours, to be used for a possible recovery.
We are using a production environment 9.2 PostgreSQL server which processes a database of about 260 GB
Is there a way to fix "wal_segsize" to about 1 Gb in 9.2. version, and "rebuild" postgreSQL server?
The goal is to drastically reduce the number of WALs.

Upgrading to 9.5, is the only way to fix this issue?

Thank you.

[Descrizione: cid:image001(dot)jpg(at)01CE4109(dot)E9653C00]
_______________________________

Gianfranco Cocco
Gruppo DBA Torino
Managed Operations - Data Center Factory
gianfranco(dot)cocco(at)eng(dot)it<mailto:gianfranco(dot)cocco(at)eng(dot)it>
Engineering.MO S.p.A
Corso Mortara, 22 - 10149 Torino
Tel. 011 19449548 (SHORT CODE: 676548)
www.eng.it<http://www.eng.it>

___________________________

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2017-06-09 14:01:20 Re: BUG #14695: Documentation is not accurate
Previous Message Joe Conway 2017-06-09 13:16:37 Re: BUG #14682: row level security not work with partitioned table

Browse pgsql-performance by date

  From Date Subject
Next Message Frits Jalvingh 2017-06-09 13:56:58 Re: Improving PostgreSQL insert performance
Previous Message Kenneth Marshall 2017-06-09 13:28:57 Re: Improving PostgreSQL insert performance