Skip site navigation (1) Skip section navigation (2)

Re: BUG #7534: walreceiver takes long time to detect n/w breakdown

From: Amit kapila <amit(dot)kapila(at)huawei(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>, Heikki Linnakangas<hlinnakangas(at)vmware(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, "pgsql-bugs(at)postgresql(dot)org"<pgsql-bugs(at)postgresql(dot)org>, "pgsql-hackers(at)postgresql(dot)org"<pgsql-hackers(at)postgresql(dot)org>
Subject: Re: BUG #7534: walreceiver takes long time to detect n/w breakdown
Date: 2012-10-02 07:43:50
Message-ID: 6C0B27F7206C9E4CA54AE035729E9C382853590D@szxeml509-mbs (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
On Monday, October 01, 2012 8:36 PM Robert Haas wrote:
On Mon, Oct 1, 2012 at 6:38 AM, Heikki Linnakangas
<hlinnakangas(at)vmware(dot)com> wrote:
>> Hmm, I think we need to step back a bit. I've never liked the way
>> replication_timeout works, where it's the user's responsibility to set
>> wal_receiver_status_interval < replication_timeout. It's not very
>> user-friendly. I'd rather not copy that same design to this walreceiver
>> timeout. If there's two different timeouts like that, it's even worse,
>> because it's easy to confuse the two.

> I agree, but also note that wal_receiver_status_interval serves
> another user-visible purpose as well.

By above do you mean to say that wal_receiver_status_interval is used for reply of data sent by server to indicate till what point receiver has flushed data or something else?

With Regards,
Amit Kapila.



In response to

pgsql-hackers by date

Next:From: Alexander KorotkovDate: 2012-10-02 07:45:56
Subject: Patch for removng unused targets
Previous:From: Amit kapilaDate: 2012-10-02 07:36:39
Subject: Re: BUG #7534: walreceiver takes long time to detect n/w breakdown

pgsql-bugs by date

Next:From: Heikki LinnakangasDate: 2012-10-02 08:26:24
Subject: Re: BUG #7534: walreceiver takes long time to detect n/w breakdown
Previous:From: Amit kapilaDate: 2012-10-02 07:36:39
Subject: Re: BUG #7534: walreceiver takes long time to detect n/w breakdown

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group