| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | Florian Pflug <fgp(at)phlo(dot)org>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, jd(at)commandprompt(dot)com, tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: beta3 & the open items list |
| Date: | 2010-06-21 11:11:56 |
| Message-ID: | AANLkTimRfJfFLQD6ktPmwVjpWmOy5YbEnXlXZe8MpRed@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 21, 2010 at 4:37 AM, Greg Stark <gsstark(at)mit(dot)edu> wrote:
> On Mon, Jun 21, 2010 at 4:54 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> I feel like we're getting off in the weeds, here. Obviously, the user
>> would ideally like the connection to the master to last forever, but
>> equally obviously, if the master unexpectedly reboots, they'd like the
>> slave to notice - ideally within some reasonable time period - that it
>> needs to reconnect.
>
>
>
>> There's no perfect way to distinguish "the master
>> croaked" from "the network administrator unplugged the Ethernet cable
>> and is planning to plug it back in any hour now", so we'll just need
>> to pick some reasonable timeout and go with it.
Eh... was there supposed to be some text here?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2010-06-21 12:49:25 | Re: Proposal for 9.1: WAL streaming from WAL buffers |
| Previous Message | Heikki Linnakangas | 2010-06-21 09:40:02 | Re: Proposal for 9.1: WAL streaming from WAL buffers |