| From: | Richard Huxton <dev(at)archonet(dot)com> |
|---|---|
| To: | Guido Neitzer <guido(dot)neitzer(at)pharmaline(dot)de> |
| Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Improving Availability |
| Date: | 2005-12-14 16:28:08 |
| Message-ID: | 43A04818.4000207@archonet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Guido Neitzer wrote:
> On 14.12.2005, at 16:46 Uhr, Richard Huxton wrote:
>
>> I'd be tempted to look at pgpool sitting between your application and
>> the database, and then replication from the one machine to the other.
>
> Right, I thought the same, BUT: I have two application servers (one on
> each machine) connecting to a network URL via JDBC. When pgpool is
> involved, I assume it only runs on one server, right?
>
> Or can I have pgpool running on both servers, each knowing about the two
> servers and the applications just connect to "localhost"?
That's the sort of thing I was thinking of. Keep the application
ignorant of the actual setup.
--
Richard Huxton
Archonet Ltd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2005-12-14 16:29:08 | Re: Improving Availability |
| Previous Message | Guido Neitzer | 2005-12-14 16:19:17 | Re: Improving Availability |