> "Mark Woodward" <[EMAIL PROTECTED]> writes: > >> The point is, that I have been working with this sort of "use case" for >> a >> number of years, and being able to represent multiple physical databases >> as one logical db server would make life easier. It was a brainstorm I >> had >> while I was setting this sort of system for the [n]th time. > > It sounds like all that would be needed is a kind of "smart > proxy"--has a list of database clusters on the machine and the > databases they contain, and speaks enough of the protocol to recognize > the startup packet and reroute it internally to the right cluster. > I've heard 'pgpool' mentioned here; from a quick look at the docs it > looks similar but not quite what you want. > > So your databases would listen on 5433, 5434, etc and the proxy would > listen on 5432 and route everything properly. If a particular cluster > is not up, the proxy could just error out the connection. > > Hmm, that'd be fun to write if I ever find the time...
It is similar to a proxy, yes, but that is just part of it. The setup and running of these systems should all be managed. ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend