Redundant Database, Pgsql ?

[David White]

If I understand open source Postgres correctly, though, this setup basically requires that the application be read-only, or at least be intelligent enough not to attempt to write to a host if it has failed over to it, right? Don't you have to have human intervention to actually fail the master / primary over for write purposes?

Sent with Proton Mail secure email.

------- Original Message -------
On Tuesday, February 21st, 2023 at 10:28 PM, Marcus Jodorf <bofh at killfile.de> wrote:


> On 2/21/23 18:04, Lars Schotte wrote:
> 

> > Yes, that looks nice, I am going to try that too.
> > 

> > Because every other option is based on some other software,
> > like relayd or nginx, it is all possible, but adds complexity.
> > 

> > The best would be to have it inside connection string.
> 

> 

> /etc/dovecot/dovecot-sql.conf.ext:
> 

> ...
> connect= host=host1 host=host2 dbname=<db> user=<user> password=<pwd>
> 

> 

> 

> I'm using that since pretty much 2006 - if I'm not mistaken - on my
> little servers. Simply works.
> 

> If one server is not reachable you just get an error log entry in
> mail.err that connect failed to the database that is down.
> But that is all - dovecot keeps working as normal.
> 

> BTW: Same with postfix. Simply list an additional fallback and it just
> works.
> 

> Best,
> 

> Marcus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: publickey - dmwhite823 at protonmail.com - 0x320CD582.asc
Type: application/pgp-keys
Size: 1739 bytes
Desc: not available
URL: <https://dovecot.org/pipermail/dovecot/attachments/20230222/d1f409fb/attachment.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 509 bytes
Desc: OpenPGP digital signature
URL: <https://dovecot.org/pipermail/dovecot/attachments/20230222/d1f409fb/attachment.sig>