From: | tushar <tushar(dot)ahuja(at)enterprisedb(dot)com> |
---|---|
To: | Beena Emerson <memissemerson(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net>, David Steele <david(at)pgmasters(dot)net>, 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>, Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com> |
Subject: | Re: increasing the default WAL segment size |
Date: | 2017-07-06 09:51:41 |
Message-ID: | 54be0042-96bd-5286-49c6-750fe3401828@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 07/06/2017 12:04 PM, Beena Emerson wrote:
> The 04-initdb-walsegsize_v2.patch has the following improvements:
> - Rebased over new 03 patch
> - Pass the wal-segsize intidb option as command-line option rathern
> than in an environment variable.
> - Since new function check_wal_size had only had two checks and was
> sed once, moved the code to ReadControlFile where it is used and
> removed this function.
> - improve comments and add validations where required.
> - Use DEFAULT_XLOG_SEG_SIZE to set the min_wal_size and
> max_wal_size,instead of the value 16.
> - Use XLogSegMaxSize and XLogSegMinSize to calculate the range of guc
> wal_segment_size instead 16 - INT_MAX.
Thanks Beena. I tested with below following scenarios and all are
working as expected
.)Different WAL segment size i.e 1,2,8,16,32,64,512,1024 at the time of
initdb
.)SR setup in place.
.)Combinations of max/min_wal_size in postgresql.conf with different
wal_segment_size.
.)shutdown the server forcefully (kill -9) / promote slave / to make
sure -recovery happened successfully.
.)with different utilities like pg_resetwal/pg_upgrade/pg_waldump
.)running pg_bench for substantial workloads (~ 1 hour)
.)WAL segment size is not default (changed at the time of ./configure) +
different wal_segment_size (at the time of initdb) .
Things looks fine.
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro HORIGUCHI | 2017-07-06 09:54:47 | Re: hash index on unlogged tables doesn't behave as expected |
Previous Message | Dean Rasheed | 2017-07-06 09:30:21 | Re: Multi column range partition table |