From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, 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-03 20:38:35 |
Message-ID: | CANP8+jJg7Z92_OBEJc5vHjk0pc1GdaD-a5DWze_F6xkm1682DA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 3 January 2017 at 16:24, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Jan 3, 2017 at 11:16 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> On 3 January 2017 at 15:44, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>>> Yeah. I don't think there's any way to get around the fact that there
>>> will be bigger latency spikes in some cases with larger WAL files.
>>
>> One way would be for the WALwriter to zerofill new files ahead of
>> time, thus avoiding the latency spike.
>
> Sure, we could do that. I think it's an independent improvement,
> though: it is beneficial with or without this patch.
The latency spike problem is exacerbated by increasing file size, so I
think if we are allowing people to increase file size in this release
then we should fix the knock-on problem it causes in this release
also. If we don't fix it as part of this patch I would consider it an
open item.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Pryzby | 2017-01-03 20:54:23 | Re: ALTER TABLE .. ALTER COLUMN .. ERROR: attribute .. has wrong type |
Previous Message | Tom Lane | 2017-01-03 20:35:34 | Re: ALTER TABLE .. ALTER COLUMN .. ERROR: attribute .. has wrong type |