On Sun, 2004-11-07 at 21:16, Christopher Browne wrote:
> None of these systems _directly_ address how apps would get pointed to
> the shifting servers.
<snip>
> Something needs to be "smart enough" to point apps to the right place;
> that's something to think about...
Seems like it would be pretty easy to be smart in PHP:
function db_connect() {
$conn = pg_connect("dbname='foo' user='dawg' password='HI!'
host='master'");
if (!($conn AND (pg_connection_status($conn) == 0))) {
// problem with master
$conn = pg_connect("dbname='foo' user='dawg' password='HI!'
host='replica'");
if ($conn AND (pg_connection_status($conn) == 0)) {
return $conn;
}
} else {
return $conn;
}
return NULL;
}
Whatever client-side language one uses, the technique is the same
(though the coding style might differ :P ), can be used for persistent
connections (eg: with pg_pconnect in PHP), and seems like it could be
extended to any reasonable number of database servers.
What is the problem with this? The only issue I can see is that
"replica" might be behind. Depending on the application, this might not
be bad. If the app MUST have the very most accurate DB, you could remove
the logic that connects to the replica, but then that nullifies this
whole conversation...
\<.