ould this setup work for failover, or is it only for situations where a
user might exist on primary.example.com but not on backup.example.com?
--
Dave Pooser
Cat-Herder-in-Chief, Pooserville.com
"...Life is not a journey to the grave with the intention of arriving
safely in one pretty and wel
and too exhausted to put in the
Google-time looking for a step-by-step guide. Maybe this evening, unless
you can hit me with a step-by-step off the top of your head.
--
Dave Pooser
Cat-Herder-in-Chief, Pooserville.com
"...Life is not a journey to the grave with the intention of arriving
safely
ight as well file a bug with Oracle, not that I expect them to be in any
hurry to improve compatibility with a rival DB.
--
Dave Pooser
Cat-Herder-in-Chief, Pooserville.com
"...Life is not a journey to the grave with the intention of arriving
safely in one pretty and well-preserved piece,
[1385] |104232| 760|FUNC |GLOB |0|12 |ldap_sasl_bind
[1309] |104992| 327|FUNC |GLOB |0|12 |ldap_sasl_bind_s
It seems there's some magic incantation to REALLY bind that I'm just not
seeing here. Any help gratefully accepted.
--
Dave Pooser
Cat-H
possibly try symlinking that to the version-numbered library.
Yep, and I did that to get past the configure problems, which allows me to
encounter a whole new problem in make :^)
>If all else fails you could --disable-thread-safety.
Is that safe to do on a server with a few dozen concurrent user
es in fact have the function it's griping about
(ldap_simple_bind) in both the 32-bit and 64-bit versions.
--
Dave Pooser
Cat-Herder-in-Chief, Pooserville.com
"...Life is not a journey to the grave with the intention of arriving
safely in one pretty and well-preserved piece, but to sl
record with zero length at 0/2501DBB4
LOG: redo is not required
LOG: autovacuum launcher started
LOG: database system is ready to accept connections
Any pointers would be appreciated; I'm far from an expert on either
Solaris or PostgreSQL, so it's very possible that I'm making o
