i didnt pick up on the fact that this was auth stuff, and not indexes
(indices?) or other data. LDAP is a hierarchical database, where the
relationship between data is forced into a superior/subordinate
structure. if you ask enough people, they will say that LDAP is not an
authentication
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Wed, 2023-02-22 at 11:08 +, Marc wrote:
> I don't even get what the advatages are of doing this with sql. If you
> use local replicated ldap and use local credential caching then your
> master ldap can go down without issues, even the local
think about this, you have connect= host=host1 host=host2 ...
when host1 fails, you must kick that host while it is down, each and
every single time you want a new connection to the database. there is no
record saying that box is down, no logic in the app saying i've already
tried that box,
I don't even get what the advatages are of doing this with sql. If you use
local replicated ldap and use local credential caching then your master ldap
can go down without issues, even the local caching handle some local slapd
issues.
I guess the local caching is also faster. Afaik were
On 2/22/23 11:29, David White wrote:
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
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
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.
Lars Schotte skrev den 2023-02-21 18:04:
Yes, that looks nice, I am going to try that too.
+1
Because every other option is based on some other software,
like relayd or nginx, it is all possible, but adds complexity.
+1
The best would be to have it inside connection string.
real fix or
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.
On Sun, 2023-02-19 at 17:34 +, David White wrote:
> Take a look
let me preface all of this by saying i dont have PostgreSQL running in
any fashion, but have come across footprints that are standing in a
Production environment.
are you running a single primary R/W node, with multiple secondary R/O
nodes? from what i have seen/heard, PG does not really
yes that seems to be the approach
i setup a dns entry and pointed to 3 servers
it does work round robin (ie from main, secondary etc) but that is ok
at least it is working when i take the main server offline for maintenance !
Happy Tuesday !!!
Thanks - paul
Paul Kudla
Scom.ca Internet
Paul Kudla skrev den 2023-02-19 16:01:
May I please get some guidance on what to add to talk to another
postgresql server (i have 6 replicated servers so would probably want
a couple worst case issue)
change host=localhost to host=some-other-hostname-with-multiple-ips :)
then dovecot with
It sounds like you want your application (Dovecot) to gracefully failover.
Take a look at
https://www.citusdata.com/blog/2021/02/12/reconnecting-your-app-after-a-postgres-failover/.
Perhaps that's what you're looking for, namely, the section on "Multi-Hosts
Connection Strings, thanks to libpq"
13 matches
Mail list logo
