| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | Cocco Gianfranco <Gianfranco(dot)Cocco(at)eng(dot)it>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>, DBA <DBA(at)italiaonline(dot)it> |
| Subject: | Re: Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 |
| Date: | 2017-06-12 21:25:57 |
| Message-ID: | CAB7nPqQvRY+-UQ0Q5OrL-55d5gr+naHBZnxyvBZS5rYipLQj3g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-performance |
On Tue, Jun 13, 2017 at 2:27 AM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> But there is something preventing it. wal_segsize cannot exceed 64MB in
> 9.2. v10 will be the first version which will allow sizes above 64MB.
Yes, indeed. I have misread --with-segsize and --with-wal-segsize in
the docs. Sorry for the confusion.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | girgen | 2017-06-12 21:52:51 | BUG #14702: Streaming replication broken after server closed connection unexpectedly |
| Previous Message | Jeff Janes | 2017-06-12 17:27:58 | Re: Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Cocco Gianfranco | 2017-06-13 09:10:50 | R: Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 |
| Previous Message | Jeff Janes | 2017-06-12 17:27:58 | Re: Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 |