Re: [HACKERS] increasing the default WAL segment size - Mailing list pgsql-hackers

From Beena Emerson
Subject Re: [HACKERS] increasing the default WAL segment size
Date
Msg-id CAOG9ApHMu33KutixFrf3LHZsCJyeqNp7+nh+KsXf8u3utRxYFg@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] increasing the default WAL segment size  (tushar <tushar.ahuja@enterprisedb.com>)
Responses Re: [HACKERS] increasing the default WAL segment size  (tushar <tushar.ahuja@enterprisedb.com>)
Re: [HACKERS] increasing the default WAL segment size  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Hello,

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.ahuja@enterprisedb.com> wrote:

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 .

Removed.
 

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

EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Attachment

pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: [HACKERS] Performance improvement for joins where outer side is unique
Next
From: Michael Paquier
Date:
Subject: [HACKERS] Re: [COMMITTERS] pgsql: Add test case for two phase commit. Also byMasahiko Sawada.