Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nUaBl-0007JZ-K0 for pgsql-general@arkaria.postgresql.org; Wed, 16 Mar 2022 20:24:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nUaBk-0007sb-H8 for pgsql-general@arkaria.postgresql.org; Wed, 16 Mar 2022 20:24:08 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nUaBi-0007sP-PS for pgsql-general@lists.postgresql.org; Wed, 16 Mar 2022 20:24:08 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nUaBd-0000uz-CX for pgsql-general@lists.postgresql.org; Wed, 16 Mar 2022 20:24:05 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 6B6305C0225; Wed, 16 Mar 2022 16:23:59 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Wed, 16 Mar 2022 16:23:59 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm3; bh=ZF0rcr54LSDEEu imlAGre8Q8pwvRc2TSo2vzBuziVmk=; b=QbuxN/+06UmDOHaXvnq2seOe2FPgSi +HzU3RwxGtBVErnZHAQ4o984Yu8P0gHEnoSMi54QkT3Hzp8fP5GiUKFtYgOQ+vdX xsXv7M6/QsPOhCFbqtBTvI47R54hTA9nPh6ZNnnxmpjUwAGMhYVXhSr6S++Fdd4f Cd5/Ke4cEFxX8LK0i67+xRGuLMvojP9nexjht+BaJ+gkBU/PcI+othyAGq24zyvL 3aom+n666MeVcuOpU9eh66JEZCnba8Pt0DAfg0wkouBQyWnCtOtCQQH61k8zNOQ2 iqA1Byd1H/o+VmAK8ki8I1oKeL0QrYArCslHiswMq4owsdPt+zlmRT6g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:date:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; bh=ZF0rcr54LSDEEuimlAGre8Q8pwvRc2TSo2vzBuziVmk=; b=RH/Bh8bO SkYg9FpooQJOyE/flK9l7x1ouFTW2vVFCMe4BqbGqoqNEvlHdUtVO6T3JcbGRL28 Mu55C4xtZUPwMrhmvnqIGexcDtp+bfcLKWnQnUhfVhFVbUahsciyFlEMjLDLXrdY G2a+sNHSIWghU/ci1iEnBV3onj24XHloUDyl8M8XRJREQeCZ9q5PQyqV23RBIpv4 UUJGK0dMJjR3LdZgUZ24Ad3PFeGWlSLLZo40rMSAtfgul3E/NrtoTRl0nLvOD8b/ KWhKEuybtCJkiDtnKnPgy+PAHnQmDzHBKrFNIMMD9bJXf3/SIuvWBjNSxfvWV7fI GNBQMxiGmKEl8g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrudefvddgudeffecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpeetughr ihgrnhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtg homheqnecuggftrfgrthhtvghrnhepvedvkeeihfduhffhtdekleegffduiefgteejgeff gffhteefleeludfgleelgeevnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpe hmrghilhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 16 Mar 2022 16:23:58 -0400 (EDT) Message-ID: <14e1cc7f-c2e7-81b7-4d6a-086fb5fdef10@aklaver.com> Date: Wed, 16 Mar 2022 13:23:58 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Subject: Re: Apparently table locks are the key issue to see red flags Content-Language: en-US To: Shaozhong SHI , pgsql-general References: From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 3/16/22 13:15, Shaozhong SHI wrote: > > > Apparently table locks are the key issue to see red flags. > > As we observe, every time, red marking occurs, there must be some tables > are locked. > > Can anyone shed light into this? Not with the information provided. Needed info(and you should know this by now): 1) Postgres version 2) Definition of red flags? 3) How do you observe the tables locked? 4) The results of the process you use in 3) > > Regards, > > David -- Adrian Klaver adrian.klaver@aklaver.com