Re: increasing the default WAL segment size

From: Beena Emerson <memissemerson(at)gmail(dot)com>
To: tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>, Prabhat Sahu <prabhat(dot)sahu(at)enterprisedb(dot)com>
Cc: 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-14 05:44:09
Views: Raw Message | Whole Thread | Download mbox
Lists: pgsql-hackers


Attached is the updated patch. It fixes the issues and also updates few
code comments.

On Fri, Mar 10, 2017 at 1:09 PM, tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>
> 1)at the time of initdb, we have set - "--wal-segsize 4" ,so all the WAL
> file size should be 4 MB each but in the postgresql.conf file , it is
> mentioned
> #wal_keep_segments = 0 # in logfile segments,* 16MB each*; 0
> disables

> so the comment (16MB ) mentioned against parameter 'wal_keep_segments'
> looks wrong , either we should remove this or modify it .


> 2)Getting "Aborted (core dumped)" error at the time of running
> pg_basebackup ,
> *(this issue is only coming on Linux32 ,not on Linux64) * we have double
> check to confirm it .

Can you please check with the new patch?

Thank you,

Beena Emerson

The Enterprise PostgreSQL Company

Attachment Content-Type Size
02-initdb-walsegsize-v4.patch application/octet-stream 34.6 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2017-03-14 06:18:43 Re: [COMMITTERS] pgsql: Add test case for two phase commit. Also by Masahiko Sawada.
Previous Message David Rowley 2017-03-14 05:37:24 Re: Performance improvement for joins where outer side is unique