Re: Add Information during standby recovery conflicts

From: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
To: "Drouvot, Bertrand" <bdrouvot(at)amazon(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Add Information during standby recovery conflicts
Date: 2021-01-08 06:24:36
Message-ID: a3c674ba-9134-1044-f0ee-8f3462efd984@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2021/01/08 14:02, Drouvot, Bertrand wrote:
> Hi,
>
> On 1/7/21 4:51 PM, Fujii Masao wrote:
>> Thanks for the review! I pushed the latest patch.
>>
> Thanks all of you for your precious help on this patch!
>
> The original idea behind this thread has been split into 3 pieces.
>
> Pieces 1 (9d0bd95fa90a7243047a74e29f265296a9fc556d) and 2 (0650ff23038bc3eb8d8fd851744db837d921e285) have now been committed, the last one is to add more information regarding the canceled statements (if any), like:
>
> * What was the blocker(s) doing?

This "canceled statement" is just one that's canceled by recovery conflict?
If so, the blocker is always the startup process? Sorry maybe I fail to
understand this idea well..

> * When did the blocker(s) started their queries (if any)?

If the blocker is the startup process, it doesn't start any query at all?

Anyway if you post the patch, I'm happy to review that!

Regards,

--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Drouvot, Bertrand 2021-01-08 06:42:46 Re: Add Information during standby recovery conflicts
Previous Message Pavel Stehule 2021-01-08 06:20:50 Re: proposal: schema variables