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

From Michael Paquier
Subject Re: increasing the default WAL segment size
Date
Msg-id CAB7nPqSQzvucB635Yp0+9JrcbDGHwcBDdxKNb-wDGLw-UFUruQ@mail.gmail.com
Whole thread Raw
In response to Re: increasing the default WAL segment size  (Bruce Momjian <bruce@momjian.us>)
Responses Re: increasing the default WAL segment size  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
On Thu, Aug 25, 2016 at 10:25 PM, Bruce Momjian <bruce@momjian.us> wrote:
> On Wed, Aug 24, 2016 at 10:40:06PM -0300, Claudio Freire wrote:
>> > time instead of requiring a recompile; we probably don't save any
>> > significant number of cycles by compiling this into the server.
>>
>> FWIW, +1
>>
>> We're already hurt by the small segments due to a similar phenomenon
>> as the ssh case: TCP slow start. Designing the archive/recovery
>> command to work around TCP slow start is quite complex, and bigger
>> segments would just be a better thing.
>>
>> Not to mention that bigger segments compress better.
>
> This would be good time to rename pg_xlog and pg_clog directories too.

That would be an excellent timing to do so. The first CF is close by,
and such a change would be better at the beginning of the  development
cycle.
-- 
Michael



pgsql-hackers by date:

Previous
From: neha khatri
Date:
Subject: Re: RFC: replace pg_stat_activity.waiting with something more descriptive
Next
From: Stephen Frost
Date:
Subject: Re: increasing the default WAL segment size