What's the purpose of such configuration? Doesn't makes sense for me. The only reasonable case where you would want to put the data folder on a shared storage is for usage with warm standby, where you can have a secondary server which serves as a read-only replica, and can be rpomoted to master on master failure. If you intend high availability, you'd rather try it at VM level, like vmware HA or Proxmox HA. That will make your VM run on any hypervisor in the group disregarding the failure of some node. Regards, Alvaro Aguayo Jefe de Operaciones Open Comb Systems E.I.R.L. Oficina: (+51-1) 3377813 | RPM: #034252 / (+51) 995540103 | RPC: (+51) 954183248 Website: www.ocs.pe ----- Original Message ----- From: "Slava Bendersky" <volga629@xxxxxxxxxxxxxx> To: "John R Pierce" <pierce@xxxxxxxxxxxx> Cc: "pgsql-general" <pgsql-general@xxxxxxxxxxxxxx> Sent: Wednesday, 30 March, 2016 10:57:13 PM Subject: Re: bdr replication In my case only virtual hosts are use share storage (feed from glusterfs), but actual virtual machines have own separate disks and all PostgreSQL run on separate data directories. volga629 ----- Original Message ----- From: "John R Pierce" <pierce@xxxxxxxxxxxx> To: "pgsql-general" <pgsql-general@xxxxxxxxxxxxxx> Sent: Thursday, 31 March, 2016 00:34:55 Subject: Re: bdr replication On 3/30/2016 8:09 PM, Slava Bendersky wrote: > Is any share storage technology recommended for PostgreSQL in virtual > environment ? > Ok what I will do is going take backups, shutdown both virtual servers > and place all vm use local disk on server only. 'share storage technology'... um. thats such a vague term, it can mean lots of things. each postgres instance needs its own data store, two instances can NOT share the same files under any condition. these data stores can be on SAN or NAS, as long the storage is reliable about committed random writes, and as long as two different servers aren't using the SAME directory for their data stores. -- john r pierce, recycling bits in santa cruz -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
