Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uf1p6-001A67-VV for pgsql-general@arkaria.postgresql.org; Thu, 24 Jul 2025 19:41:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uf1p4-00AYkh-Tc for pgsql-general@arkaria.postgresql.org; Thu, 24 Jul 2025 19:41:47 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uf1p4-00AYkY-CA for pgsql-general@lists.postgresql.org; Thu, 24 Jul 2025 19:41:46 +0000 Received: from gecko.ash.relay.mailchannels.net ([23.83.222.66]) by makus.postgresql.org with smtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1uf1p2-000bOs-0f for pgsql-general@lists.postgresql.org; Thu, 24 Jul 2025 19:41:45 +0000 X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 4F658903811; Thu, 24 Jul 2025 19:41:41 +0000 (UTC) Received: from pdx1-sub0-mail-a290.dreamhost.com (100-114-148-227.trex-nlb.outbound.svc.cluster.local [100.114.148.227]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id DAD3B903222; Thu, 24 Jul 2025 19:41:40 +0000 (UTC) ARC-Seal: i=1; s=arc-2022; d=mailchannels.net; t=1753386100; a=rsa-sha256; cv=none; b=LlKB6jG2iHVewVm5WlqciJh6JqUcbEnkeiuqBb3dwVqi+ROeOFNlhuck8FnyCrIMZ2G9iY yLC+LY4U3j1d0gs8wTduEuZlqQJv0RdU+Re5yzlY7qDBKR5+bMIy9BcSfX/phc6fKOCChn YUvfVR0WlqFsM8kBgfjuAFnEMJeukpFLLEovzvpeoXj/jteOWuolcA0zQ23yxCwiRB1/gY n1yp7sRu5z2wFKpfs4U8LoOoh0j8b2u5AUkchemcdnxhYyF3eLuP3vdNNI/e5EFE9QxR6C tn2b5/iR/nYvk9+RvFRg31iICVqn8GZ7vDQSF2d0/s5By+LLpepnguu1NGegPA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=mailchannels.net; s=arc-2022; t=1753386100; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references:dkim-signature; bh=uAZ9Yp3KKHIt31bfAzJqKw2z6S8pZo5caFeqG3TlCJo=; b=qNlWa5e1F3F52BPJG4BShMSh4M3RXUKSd6lOZ+2R1jS9Z+hZJwIhPMavHXOhqGQLPevyHS mVtXA+7cjLsAPxOFlhFT5ar9LpZZ0zpj745/qntcsRC95H6pPpSJ5LcwLnWN/SmdS0tk3E APA9/ZQMqczNbVeqiFHzk0gVnsLLUzsJp3DoeVUJfibnLj/88BqIEOdJqUId8VboXxJPXw H/ddl8GgJYp5TXlNf1iDz1zqyz6rJnYse0E82qbqIFMbxhWB2QVoSf/bhWlJJ1iV7C3/4q 5Iu6MyXhDy0ubfSLcpYwzC2ZYYVaOvGdsO3Q8YyKBRr3sX8e6ym+9PSg+ax+VA== ARC-Authentication-Results: i=1; rspamd-7df5bc8bc6-rzmg5; auth=pass smtp.auth=dreamhost smtp.mailfrom=nico@cryptonector.com X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com X-MC-Relay: Neutral X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com X-MailChannels-Auth-Id: dreamhost X-Power-Language: 61a6b0676c189af2_1753386101135_2974316741 X-MC-Loop-Signature: 1753386101135:3260046965 X-MC-Ingress-Time: 1753386101135 Received: from pdx1-sub0-mail-a290.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384) by 100.114.148.227 (trex/7.1.3); Thu, 24 Jul 2025 19:41:41 +0000 Received: from ubby (syn-075-081-095-064.res.spectrum.com [75.81.95.64]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by pdx1-sub0-mail-a290.dreamhost.com (Postfix) with ESMTPSA id 4bp1bS1tGyzB9; Thu, 24 Jul 2025 12:41:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cryptonector.com; s=dreamhost; t=1753386100; bh=uAZ9Yp3KKHIt31bfAzJqKw2z6S8pZo5caFeqG3TlCJo=; h=Date:From:To:Cc:Subject:Content-Type; b=LSySe0pqpLoMQVUtnUddZcQUYa2caVXeA6vWhARkD4Wdx2Kjjsh0i/MKHNEhjfJ5s WlH/sl6aBrAtWJ58xHigLm0IAbsH875qiJCkJSKucvybIA98fZJqwsLPLkVbjL49fr ShFWr5wVeX9+wedw1glrCZJuyUArC15gQojL/seqQ5g2lSd+DpHTaZWIjuxlTDfk+M 12W6Icwqy/rdUz6UJOXJUFxuTPtaw8qTc6TTaMbw9gtGAd94jWF0hZmPry+SaSMs20 IUdjBVBlVeUBVNCJqqFJ5J2fl/XPHn5XwkUg3JMuPHkqlgS9mPMDhNDWP1ilGqZyoV 2QZK2+HD24Vzg== Date: Thu, 24 Jul 2025 14:41:37 -0500 From: Nico Williams To: Laurenz Albe Cc: Pierre Barre , pgsql-general@lists.postgresql.org Subject: Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Message-ID: References: <3345416f84147603587ff8656cc3ac95b6787744.camel@cybertec.at> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3345416f84147603587ff8656cc3ac95b6787744.camel@cybertec.at> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Jul 18, 2025 at 06:40:58AM +0200, Laurenz Albe wrote: > On Fri, 2025-07-18 at 00:57 +0200, Pierre Barre wrote: > > Looking forward to your feedback and questions! > > I think the biggest hurdle you will have to overcome is to > convince notoriously paranoid DBAs that this tall stack > provides reliable service, honors fsync() etc. Is there a test suite that can be used to test PG's ACIDity in the face of simulated power failures? > Performance is great, but it is not everything. If things > perform surprisingly well, people become suspicious. +1 > > P.S. The full project includes a custom NFS filesystem too. > > "NFS" is a key word that does not inspire confidence in > PostgreSQL circles... Certainly NFSv3 should. NFSv4 is much safer but I've no experience running PG on it and I assume there will be cases where recovery from network and/or server failures is slow.