Actually what I want is multiple Postgres instances to have read and write access to the same data storage directory. Anyway, that can not be possible as what you say. 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?
Finally, my question is, why the scenario is different for MySQL and Postgres? Could you please help me to figure out the issue? This is for my Final year project testing Kubernetes using fuzzing.
Not sure what you're trying to accomplish, but PostgreSQL can definitely not share storage between active postmasters. Nor can MySQL, afaik.
Finally, my question is, why the scenario is different for MySQL and Postgres? Could you please help me to figure out the issue? This is for my Final year project testing Kubernetes using fuzzing.
Not sure what you're trying to accomplish, but PostgreSQL can definitely not share storage between active postmasters. Nor can MySQL, afaik.
