public inbox for [email protected]  

help / color / mirror / Atom feed

From: Laurenz Albe <[email protected]>
To: first last <[email protected]>
To: Alan Hodgson <[email protected]>
Cc: [email protected]
Cc: [email protected]
Subject: Re: Access a Postgres storage with two independent instances
Date: Tue, 07 May 2024 13:17:35 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAG3FJTamrfzk4k+KC+bTn0axMrPqj9yaoYOzmoiRX5n90QcTFg@mail.gmail.com>
References: <CAG3FJTaRdS1asGHcuMk3NFB0Ap+kcjO7mk1gMY2jSZ4T0a_62A@mail.gmail.com>
	<[email protected]>
	<CAG3FJTamrfzk4k+KC+bTn0axMrPqj9yaoYOzmoiRX5n90QcTFg@mail.gmail.com>

On Tue, 2024-05-07 at 09:56 +0530, first last wrote:
> But, when I deploy MySQL/MongoDB deployment with multiple replicas to
> access the same storage, the all pods except one become CrashLoopBackOff
> state. This is happening for MySQL/Mongo. When it comes to Postgres, I
> deployed it with multiple pods, all the pods became healthy and there is
> no such CrashLoopBackOff state occurred. But those pods access different
> storages for every pod. Why this totally different from MySQL and Mongo?

Because it is different software?

"Why" questions are notoriously hard to answer (as anyone knows who has
ever had children).  Shared-storage architectures are not great, because
they have a single point of failure and only scale very moderately.  So
there are no efforts in PostgreSQL to make that work.

Yours,
Laurenz Albe

view thread (5+ messages)  latest in thread

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], [email protected], [email protected], [email protected]
  Subject: Re: Access a Postgres storage with two independent instances
  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