| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Cocco Gianfranco <Gianfranco(dot)Cocco(at)eng(dot)it> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>, DBA <DBA(at)italiaonline(dot)it> |
| Subject: | Re: [BUGS] Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 |
| Date: | 2017-06-13 20:38:52 |
| Message-ID: | CAB7nPqQTYcMC=_29F1MLAXOqvPe-ExckVL623OP581YAxoiF4A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-performance |
On Tue, Jun 13, 2017 at 10:39 PM, Cocco Gianfranco
<Gianfranco(dot)Cocco(at)eng(dot)it> wrote:
> ./configure --with-wal-segsize=1024
>
> checking for WAL segment size... configure: error: Invalid WAL segment size.
> Allowed values are 1,2,4,8,16,32,64.
>
> Please, how can I do?
When trying to compile Postgres 9.6, the maximum value is 64. If you
want to allow 1GB of WAL segment size you will need to wait for 10, or
just use 64MB.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2017-06-13 23:08:12 | Re: Re: BUG #14680: startup process on standby encounter a deadlock of TwoPhaseStateLock when redo 2PC xlog |
| Previous Message | Peter Eisentraut | 2017-06-13 19:04:35 | Re: Concurrent ALTER SEQUENCE RESTART Regression |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lutz Fischer | 2017-06-15 08:06:39 | Using array instead of sub table (storage and speed) |
| Previous Message | Michael Paquier | 2017-06-13 09:34:20 | Re: [BUGS] Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 |