From: Joshua D. Drake <jd@commandprompt.com>
To: Andres Freund <andres@anarazel.de>
Cc: pgsql-general@postgresql.org
Cc: pgsql-performance@postgresql.org
Subject: Re: Questionaire: Common WAL write rates on busy servers.
Date: Thu, 27 Apr 2017 10:29:48 -0700
Message-ID: <80f280c1-910f-7eae-33a2-fd0cfc9ee8c9@commandprompt.com> (raw)
In-Reply-To: <20170427163407.dtqi6v57bj4tiu5c@alap3.anarazel.de>
References: <20170425041743.ddabv2mwevcmtx5a@alap3.anarazel.de>
<20170427155906.uudovtd62x56brmx@alap3.anarazel.de>
<a842fbdf-b761-bf21-47dd-cd87d05a8d04@commandprompt.com>
<20170427163407.dtqi6v57bj4tiu5c@alap3.anarazel.de>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
On 04/27/2017 09:34 AM, Andres Freund wrote:
> On 2017-04-27 09:31:34 -0700, Joshua D. Drake wrote:
>> On 04/27/2017 08:59 AM, Andres Freund wrote:
>>
>> I would agree it isn't yet a widespread issue.
>
> I'm not yet sure about that actually. I suspect a large percentage of
> people with such workloads aren't lingering lots on the lists.
That would probably be true. I was thinking of it more as the "most new
users are in the cloud" and the "cloud" is going to be rare that a cloud
user is going to be able to hit that level of writes. (at least not
without spending LOTS of money)
>
>
>> The only people that are likely going to see this are going to be on bare
>> metal. We should definitely plan on that issue for say 11.
>
> "plan on that issue" - heh. We're talking about major engineering
> projects here ;)
Sorry, wasn't trying to make light of the effort. :D
>
>
>> I do have a question though, where you have seen this issue is it with
>> synchronous_commit on or off?
>
> Both. Whether that matters or not really depends on the workload. If you
> have bulk writes, it doesn't really matter much.
Sure, o.k.
Thanks,
Andres
>
> - Andres
>
--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.
Unless otherwise stated, opinions are my own.
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: jd@commandprompt.com, andres@anarazel.de, pgsql-general@postgresql.org
Subject: Re: Questionaire: Common WAL write rates on busy servers.
In-Reply-To: <80f280c1-910f-7eae-33a2-fd0cfc9ee8c9@commandprompt.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox