On Sun, Nov 15, 2020 at 12:48 AM Mohamed Wael Khobalatte <
mkhobala...@grubhub.com> wrote:
>
>
> On Sat, Nov 14, 2020 at 2:46 PM Radoslav Nedyalkov
> wrote:
>
>>
>>
>> On Fri, Nov 13, 2020 at 8:13 PM Radoslav Nedyalkov
>> wrote:
>>
>>>
>>>
>>> On Fri, Nov 13, 2020 at 7:37 PM Laurenz Albe
>>> wr
On Sat, Nov 14, 2020 at 2:46 PM Radoslav Nedyalkov
wrote:
>
>
> On Fri, Nov 13, 2020 at 8:13 PM Radoslav Nedyalkov
> wrote:
>
>>
>>
>> On Fri, Nov 13, 2020 at 7:37 PM Laurenz Albe
>> wrote:
>>
>>> On Fri, 2020-11-13 at 15:24 +0200, Radoslav Nedyalkov wrote:
>>> > On a very busy master-standby s
On Fri, Nov 13, 2020 at 8:13 PM Radoslav Nedyalkov
wrote:
>
>
> On Fri, Nov 13, 2020 at 7:37 PM Laurenz Albe
> wrote:
>
>> On Fri, 2020-11-13 at 15:24 +0200, Radoslav Nedyalkov wrote:
>> > On a very busy master-standby setup which runs typical olap processing -
>> > long living , massive writes
On Fri, Nov 13, 2020 at 7:37 PM Laurenz Albe
wrote:
> On Fri, 2020-11-13 at 15:24 +0200, Radoslav Nedyalkov wrote:
> > On a very busy master-standby setup which runs typical olap processing -
> > long living , massive writes statements, we're getting on the standby:
> >
> > ERROR: canceling st
On Fri, 2020-11-13 at 15:24 +0200, Radoslav Nedyalkov wrote:
> On a very busy master-standby setup which runs typical olap processing -
> long living , massive writes statements, we're getting on the standby:
>
> ERROR: canceling statement due to conflict with recovery
> FATAL: terminating co
Hi Forum,all
On a very busy master-standby setup which runs typical olap processing -
long living , massive writes statements, we're getting on the standby:
ERROR: canceling statement due to conflict with recovery
FATAL: terminating connection due to conflict with recovery
The weird thing is