Re: increasing the default WAL segment size

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Beena Emerson <memissemerson(at)gmail(dot)com>
Subject: Re: increasing the default WAL segment size
Date: 2017-01-04 15:33:27
Message-ID: CA+TgmobRWrVDUaHf1YbYxN-LYT1JD36Pw4=K_Zz4PeavNfEukw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jan 4, 2017 at 9:47 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On 4 January 2017 at 13:57, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> On Wed, Jan 4, 2017 at 3:05 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>>> Strange response. Nothing has been assumed. I asked for tests and you
>>> provided measurements.
>>
>> Sure, of zero-filling a file with dd. But I also pointed out that in
>> a real PostgreSQL cluster, the change could actually *reduce* latency.
>
> I think we are talking at cross purposes. We agree that the main
> change is useful, but it causes another problem which I can't see how
> you can characterize as reduced latency, based upon your own
> measurements.

Zero-filling files will take longer if the files are bigger. That
will increase latency. But we will also have fewer forced
end-of-segment syncs. That will reduce latency. Which effect is
bigger?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2017-01-04 15:36:25 Re: emergency outage requiring database restart
Previous Message Tom Lane 2017-01-04 15:26:19 Re: [PATCH] Reload SSL certificates on SIGHUP