From: | Bèrto ëd Sèra <berto(dot)d(dot)sera(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | pooler/router? |
Date: | 2012-12-13 12:39:28 |
Message-ID: | CAKwGa_9z6Xscmo3=yWRGWNvSbzGPnaiw9L85X+57TUn=x=RDew@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi all,
I have a customer who needs to split a set of pg databases that have
outgrown any possible "big iron" and needs to do it quick, at zero
impact on lots of existing and basically undocumented applications.
I was wondering whether there is anything I can drop in as a
"middleware", that will get any incoming connections to oldserver:5432
and reroute them to a set of individual boxes, based on the targeted
database. PgPooler + routing, sort of.
Any hint is greatly appreciated.
Cheers
Bèrto
--
==============================
If Pac-Man had affected us as kids, we'd all be running around in a
darkened room munching pills and listening to repetitive music.
From | Date | Subject | |
---|---|---|---|
Next Message | Gabriele Bartolini | 2012-12-13 13:07:26 | Re: pooler/router? |
Previous Message | Haifeng Liu | 2012-12-13 10:44:56 | Confuse about the behaveior of PreparedStatement.executeBatch (jdbc) |