Re: Automatic Client Failover
От | Jonah H. Harris |
---|---|
Тема | Re: Automatic Client Failover |
Дата | |
Msg-id | 36e682920808041442u199582fxda85ed0d92110672@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Automatic Client Failover (Josh Berkus <josh@agliodbs.com>) |
Ответы |
Re: Automatic Client Failover
|
Список | pgsql-hackers |
On Mon, Aug 4, 2008 at 5:39 PM, Josh Berkus <josh@agliodbs.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
В списке pgsql-hackers по дате отправления: