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 1nUaAk-0007Eh-9S for pgsql-general@arkaria.postgresql.org; Wed, 16 Mar 2022 20:23:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nUa9k-0003tP-UZ for pgsql-general@arkaria.postgresql.org; Wed, 16 Mar 2022 20:22:04 +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 1nUa9k-0003tF-HK for pgsql-general@lists.postgresql.org; Wed, 16 Mar 2022 20:22:04 +0000 Received: from mail-ot1-x332.google.com ([2607:f8b0:4864:20::332]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nUa9i-0000ta-2i for pgsql-general@lists.postgresql.org; Wed, 16 Mar 2022 20:22:03 +0000 Received: by mail-ot1-x332.google.com with SMTP id z9-20020a05683020c900b005b22bf41872so2165624otq.13 for ; Wed, 16 Mar 2022 13:22:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :references:from:in-reply-to; bh=8Tvz4PuUxi/A9DPrKMMV8KhNleVhZ4YQ2X90TNgkUug=; b=AqyCw8j+yswdE8QrpzwpZpQDJCsP1PRMMcwE7if/Tbrg9h9ZVhnj6lHBGczgrgbZ/E wNoDiS2daCObOBK4nSBtl8TwTqF+NSjxPqmbBp5lb+xXyDru4AFZGsS9zyM1yKDd3PL+ d7afamKxwIja+yetThZJRgHbvPgoNGRSqx9Spu9esNRTj8jBsBpuxdSAz97htAaSJ3bk FSqveiPIzs4Ra3uIMZmYi3rHrm8DASD4tvxB96qvD+V7+e42xsY2RP3u/bIoqMlJFTrb bF9o0mhSiQXKE8kFB7FNxmCvvG6wB9yPKR6iyPNAjIwo/okJbYnYLopRBdXWdsdSjbIc 7m9w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to; bh=8Tvz4PuUxi/A9DPrKMMV8KhNleVhZ4YQ2X90TNgkUug=; b=OF1VwYZ95ovzRF/DKy0zZyWQqLA0ECIlOcajXTQIXtoTROxBCIlqzjy0o31NNKTy+y Bnr0GwVne0uZyas9VSI+YY/P8U9z3GFOXbEfRFahZB24daJHKbYO8HIZJEbkUxhj1ltF 4q8N83vsTtp2ioqlKXNeTv7w2Ut22lToemY0VeETtlYFKYa1YESttSkmgwd9HPV5BNvX 1aObR4QNb6QD1zbtIm5jnwAZUWEc+Ab04NoIrPcMXQJZsmul5VGvta3HkSzs4DoIIOoO lhGILmz7eSybmTix4mYMhyQypg5/Ovvz3LSDZSX5zOpaMCVZ8CQPeD7l81OQalJrtn4S wwJA== X-Gm-Message-State: AOAM533U2YNJKieus8Dott+KkaQe3DmvzAq8DJ7zAAXNX8oSNfQrQ+5q QzAMCBhWjtPHjiW721gNOEbms6UzOX4= X-Google-Smtp-Source: ABdhPJwRG5ksK7kcv+a678jzwy6pPCxXSti5JxJyUE05AZ+wHh+OUJARcAaXogcAEhg8ej1+4EpXAw== X-Received: by 2002:a05:6830:608:b0:5b2:3dce:cc51 with SMTP id w8-20020a056830060800b005b23dcecc51mr615472oti.2.1647462121007; Wed, 16 Mar 2022 13:22:01 -0700 (PDT) Received: from [192.168.88.10] (ip68-11-68-85.no.no.cox.net. [68.11.68.85]) by smtp.googlemail.com with ESMTPSA id t15-20020a056808158f00b002e331356c87sm1407887oiw.39.2022.03.16.13.22.00 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 16 Mar 2022 13:22:00 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------qKkgc9sMhC0700dnfipLgARj" Message-ID: Date: Wed, 16 Mar 2022 15:21:59 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: Apparently table locks are the key issue to see red flags Content-Language: en-US To: pgsql-general@lists.postgresql.org References: From: Ron In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------qKkgc9sMhC0700dnfipLgARj Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 3/16/22 15: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. Where do these red markings occur?  (It is physically impossible for them to occur in Postgresql because Postgresql is a daemon, and therefore does not have a GUI.) -- Angular momentum makes the world go 'round. --------------qKkgc9sMhC0700dnfipLgARj Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit On 3/16/22 15: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.

Where do these red markings occur?  (It is physically impossible for them to occur in Postgresql because Postgresql is a daemon, and therefore does not have a GUI.)

--
Angular momentum makes the world go 'round.
--------------qKkgc9sMhC0700dnfipLgARj--