You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ ] latest
[x] @next
[ ] 0.x.x (or put your version here)
Steps to reproduce or a small repository showing the problem:
Does Replication in TypeORM support auto-failover, assuming that Postgres auto-failover has already setup? Like if the master connection failed, Postgres will automatically make secondary node as the primary node, but will TypeORM automatically make the one of the slave node as the master node?
E.g. in above case, if server1 has some problem and Postgres service is unavailable, Postgres has automatically make server2 the primary node; but will TypeORM automatically change master to server2 so that read and write are supported in server2?
The text was updated successfully, but these errors were encountered:
Hey thank for your question. Typeorm use node-postresPool under the hood, so this kind of question is for them. Check for example this issue brianc/node-postgres#1075.
Uh oh!
There was an error while loading. Please reload this page.
Issue type:
[x] question
[ ] bug report
[ ] feature request
[ ] documentation issue
Database system/driver:
[ ]
cordova
[ ]
mongodb
[ ]
mssql
[ ]
mysql
/mariadb
[ ]
oracle
[x]
postgres
[ ]
cockroachdb
[ ]
sqlite
[ ]
sqljs
[ ]
react-native
[ ]
expo
TypeORM version:
[ ]
latest
[x]
@next
[ ]
0.x.x
(or put your version here)Steps to reproduce or a small repository showing the problem:
Does Replication in TypeORM support auto-failover, assuming that Postgres auto-failover has already setup? Like if the master connection failed, Postgres will automatically make secondary node as the primary node, but will TypeORM automatically make the one of the slave node as the master node?
E.g. in above case, if server1 has some problem and Postgres service is unavailable, Postgres has automatically make server2 the primary node; but will TypeORM automatically change master to server2 so that read and write are supported in server2?
The text was updated successfully, but these errors were encountered: