| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | David Steele <david(at)pgmasters(dot)net> |
| Cc: | Beena Emerson <memissemerson(at)gmail(dot)com>, tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>, Prabhat Sahu <prabhat(dot)sahu(at)enterprisedb(dot)com>, Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: increasing the default WAL segment size |
| Date: | 2017-03-21 02:54:50 |
| Message-ID: | CA+TgmoZMOz_9kNYGf5zZRC2_XhhEoQ2+stRP1CNC+=Ua2CXDHA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 20, 2017 at 7:23 PM, David Steele <david(at)pgmasters(dot)net> wrote:
> With 16MB WAL segments the filename neatly aligns with the LSN. For
> example:
>
> WAL FILE 0000000100000001000000FE = LSN 1/FE000000
>
> This no longer holds true with this patch.
It is already possible to change the WAL segment size using the
configure option --with-wal-segsize, and I think the patch should be
consistent with whatever that existing option does.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-03-21 02:58:15 | Re: Our feature change policy |
| Previous Message | Amit Kapila | 2017-03-21 02:47:43 | Re: [POC] A better way to expand hash indexes. |