| From: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
|---|---|
| To: | josh(at)agliodbs(dot)com |
| Cc: | pgsql-hackers(at)postgresql(dot)org, "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
| Subject: | Re: Automatic Client Failover |
| Date: | 2008-08-04 21:42:26 |
| Message-ID: | 36e682920808041442u199582fxda85ed0d92110672@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Aug 4, 2008 at 5:39 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> Well, it's less simple, but you can already do this with pgPool on the
> client machine.
Yeah, but if you have tens or hundreds of clients, you wouldn't want
to be installing/managing a pgpool on each. Similarly, I think an
application should have the option of being notified of a connection
change; I know that wasn't in Simon's proposal, but I've found it
necessary in several applications which rely on things such as
temporary tables. You don't want the app just blowing up because a
table doesn't exist; you want to be able to handle it gracefully.
--
Jonah H. Harris, Senior DBA
myYearbook.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2008-08-04 22:35:33 | Re: IN vs EXISTS equivalence |
| Previous Message | Josh Berkus | 2008-08-04 21:39:28 | Re: Automatic Client Failover |