| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| 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-22 19:24:58 |
| Message-ID: | 21a7f698-29a6-abcb-dac7-9a969fe9462c@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/22/17 3:09 PM, Stephen Frost wrote:
> * Robert Haas (robertmhaas(at)gmail(dot)com) wrote:
>> On Wed, Mar 22, 2017 at 1:49 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
>>> Then perhaps we do need to be thinking of moving this to PG11 instead of
>>> exposing an option that users will start to use which will result in WAL
>>> naming that'll be confusing and inconsistent. I certainly don't think
>>> it's a good idea to move forward exposing an option with a naming scheme
>>> that's agreed to be bad.
>>
>
> One of the reasons to go with the LSN is that we would actually be
> maintaining what happens when the WAL files are 16MB in size.
>
> David's initial expectation was this for 64MB WAL files:
>
> 000000010000000000000040
> 000000010000000000000080
> 0000000100000000000000CO
> 000000010000000100000000
This is the 1GB sequence, actually, but idea would be the same for 64MB
files.
--
-David
david(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2017-03-22 19:28:29 | Re: Report the number of skipped frozen pages by manual VACUUM |
| Previous Message | Mithun Cy | 2017-03-22 19:17:30 | Re: Patch: Write Amplification Reduction Method (WARM) |