| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Simon Riggs <simon(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: increasing the default WAL segment size |
| Date: | 2016-08-25 19:53:14 |
| Message-ID: | CA+TgmoacvB_Vi1HuuxHsH=cmV7XEpZ1ej2f-vgcaycp+K6c+2A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Aug 25, 2016 at 3:21 PM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> Yeah, and it's also related to the point Josh Berkus was making about
> clusters with little activity.
Right.
> Does it work to set the minimum to one WAL segment, i.e. 64MB? guc.c
> has a hardcoded minimum of 2, but I couldn't find an explanation for it.
Well, I think that when you overrun the end of one segment, you're
never going to be able to wrap around to the start of the same
segment; you're going to get sucked into needing another file.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2016-08-25 19:56:09 | Re: [COMMITTERS] pgsql: Add the "snapshot too old" feature |
| Previous Message | Bruce Momjian | 2016-08-25 19:51:10 | Re: increasing the default WAL segment size |