<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: arial,helvetica,sans-serif; font-size: 12pt; color: #000000'><br>We use Slony for replication, and route all writes to the master. We are able to tell a given box in our application to stop taking new connections but continue processing existing ones. New connections are then routed to other boxes. Once all existing connections have finished, we can do maintenance/upgrades on that box, bring it back up, and continue the process with another box.<div><br></div><div>This particular application is architected such that updates on each box are written to a queue, which is processed on the master and written to the database.</div><div><br></div><div>Scott</div><div><br><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Preston" <preston.lists@gmail.com><br><b>To: </b>"Atlanta Linux Enthusiasts" <ale@ale.org><br><b>Sent: </b>Monday, March 24, 2014 4:42:39 PM<br><b>Subject: </b>[ale] PostgreSQL question<br><br>
<font face="DejaVu Sans">Hey folks, what are you doing for some kind
of load balancing with PostgreSQL</font>? How do you handle live
migration with PostgreSQL?<br>
<br>
thoughts? pointers?<br>
<br>
Preston<br>
<pre class="moz-signature">--
Be who you are and say what you feel, because those who mind don’t matter and those who matter don’t mind.
-Dr. Seuss
</pre>
<br>_______________________________________________<br>Ale mailing list<br>Ale@ale.org<br>http://mail.ale.org/mailman/listinfo/ale<br>See JOBS, ANNOUNCE and SCHOOLS lists at<br>http://mail.ale.org/mailman/listinfo<br></div><br></div></div></body></html>