<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<blockquote
cite="mid:CACbucKkuUGsQXUrCArgvi73ukgtM9c-p8taABUKoD08iJZYmsw@mail.gmail.com"
type="cite">On Wed, Aug 8, 2012 at 4:30 PM, Philip Poten <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:philip.poten@gmail.com" target="_blank">philip.poten@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hey,<br>
<br>
running postgres (or any database) on a gluster share is an
extremely<br>
bad idea. This can and will not end well, no matter what you do.</blockquote>
</blockquote>
<br>
I still don't see why people keep saying this. I've been running
mysql on a GlusterFS volume since the 2.0 days. I know Avati agrees
with you though (though I keep trying to convince him otherwise).<br>
<br>
The only problem I've ever had was with creation or alteration of
MyISAM files as they create a temporary filename, then rename it.
This often causes an error as the rename (apparently) hasn't
completed before it tries to open again (a bug that still seems to
exist in 3.3.0).<br>
<br>
InnoDB files can actually be quite efficient on a distributed volume
if you create sufficient file segments to be distributed across
subvolumes.<br>
<br>
The only real problem would be if someone thought they could run
multiple instances of the database server. Regardless of what
filesystem they're on, relational database engines are not built to
be able to do that.<br>
</body>
</html>