public inbox for [email protected]  

help / color / mirror / Atom feed

From: Jeff Ross <[email protected]>
To: [email protected]
Subject: Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance
Date: Thu, 24 Jul 2025 16:03:34 -0600
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<CAG1bHGOzCNtDeW0W8gRO7mpW=t7BqWh-iz4kX5VRCPgt_6Tr6Q@mail.gmail.com>
	<[email protected]>
	<aIKNLuEis1DQEOGv@ubby>
	<[email protected]>

On 7/24/25 13:50, Pierre Barre wrote:

> It’s not “safe” or “unsafe”, there’s mountains of valid workloads which don’t require synchronous_commit. Synchronous_commit don’t make your system automatically safe either, and if that’s a requirement, there’s many workarounds, as you suggested, it certainly doesn’t make the setup useless.
>
> Best,
> Pierre
>
> On Thu, Jul 24, 2025, at 21:44, Nico Williams wrote:
>> On Fri, Jul 18, 2025 at 12:57:39PM +0200, Pierre Barre wrote:
>>> - Postgres configured accordingly memory-wise as well as with
>>>    synchronous_commit = off, wal_init_zero = off and wal_recycle = off.
>> Bingo.  That's why it's fast (synchronous_commit = off).  It's also why
>> it's not safe _unless_ you have a local, fast, persistent ZIL device
>> (which I assume you don't).
>>
>> Nico
>> --
This then begs the obvious question of how fast is this with 
synchronous_commit = on?

reply

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: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox