pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Drouvot, Bertrand <bdrouvot@amazon.com>
To: Fujii Masao <masao.fujii@oss.nttdata.com>
To: Masahiko Sawada <sawada.mshk@gmail.com>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
To: Masahiko Sawada <masahiko.sawada@2ndquadrant.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Add Information during standby recovery conflicts
Date: Fri, 8 Jan 2021 06:02:51 +0100
Message-ID: <6e5b7836-06a2-0a0a-0ef9-a6572789cc6b@amazon.com> (raw)
In-Reply-To: <2ae8a3a6-9647-b08f-90c3-bd57a14755f9@oss.nttdata.com>
References: <fafa607c-9e85-b742-ab46-2ee807ab9364@oss.nttdata.com>
	<20201130182528.GA1854@alvherre.pgsql>
	<CAD21AoBOFs4XUHO2NOhbmaZ=pG1C1eCZrnaawAe_vFEsGvUD-g@mail.gmail.com>
	<594f4419-62aa-c272-ef7d-4287e5c6b654@amazon.com>
	<a4d89c01-9084-24f7-f591-bb10080e32d8@oss.nttdata.com>
	<CAD21AoDzCZWuMdiMtLcGnZpkoQBjV=QHmO=1CN5nFoyQmJoQCg@mail.gmail.com>
	<627f702d-a04c-b72b-b94f-214f448e2935@oss.nttdata.com>
	<73037867-b688-c5cc-5f6d-ad73db6ab94d@amazon.com>
	<CAD21AoDLzzZp_3qs7XwRZDV_-AHNW8ZUyQh8Hj1m-Sm+Wv9wGA@mail.gmail.com>
	<02b17df8-cf11-7e5a-31e3-d94c87b28775@oss.nttdata.com>
	<d78ead3f-b7e1-74ab-7b61-6065bbf8f6c1@oss.nttdata.com>
	<e6fa6cc8-8314-a64d-7bf7-ed78dfd2d9dd@oss.nttdata.com>
	<5517bbfd-27ad-3e97-51e2-cb9ffb8f8a8d@amazon.com>
	<2ae8a3a6-9647-b08f-90c3-bd57a14755f9@oss.nttdata.com>

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?
* When did the blocker(s) started their queries (if any)?
* What was the blocker(s) waiting for? on which wait event?

Does this proposal sound good to you? If so I'll start a new thread with 
a patch proposal.

Bertrand






view thread (82+ messages)  latest in thread

Message-ID: <6e5b7836-06a2-0a0a-0ef9-a6572789cc6b@amazon.com>
Permalink:  ../6e5b7836-06a2-0a0a-0ef9-a6572789cc6b@amazon.com/
Also on:    postgresql.org/message-id/6e5b7836-06a2-0a0a-0ef9-a6572789cc6b@amazon.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: bdrouvot@amazon.com, masao.fujii@oss.nttdata.com, sawada.mshk@gmail.com, alvherre@alvh.no-ip.org, horikyota.ntt@gmail.com, masahiko.sawada@2ndquadrant.com
  Subject: Re: Add Information during standby recovery conflicts
  In-Reply-To: <6e5b7836-06a2-0a0a-0ef9-a6572789cc6b@amazon.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox