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 CAOG9ApHsL2aKNaT0Y5KRi5GN=3AhdXRSS_934DsE7-FYu42grA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] increasing the default WAL segment size  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [HACKERS] increasing the default WAL segment size  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Re: [HACKERS] increasing the default WAL segment size  (Kuntal Ghosh <kuntalghosh.2007@gmail.com>)
List pgsql-hackers
Hello,


On Wed, Mar 22, 2017 at 9:19 AM, Robert Haas <robertmhaas@gmail.com> wrote:

I'm a little worried that this whole question of changing the file
naming scheme is a diversion which will result in torpedoing any
chance of getting some kind of improvement here for v11.  I don't
think the patch is all that far from being committable but it's not
going to get there if we start redesigning the world around it.


As stated above, the default 16MB has not changed and so we can take this separately and not as part of this patch. 

PFA an updated patch which fixes a minor bug I found. It only increases the string size in pretty_wal_size function.
The 01-add-XLogSegmentOffset-macro.patch has also been rebased. 

--
Thank you, 

Beena Emerson

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

pgsql-hackers by date:

Previous
From: vinayak
Date:
Subject: Re: [HACKERS] ANALYZE command progress checker
Next
From: Ashutosh Bapat
Date:
Subject: Re: [HACKERS] Partition-wise join for join between (declaratively)partitioned tables