Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qt7KT-00AuXe-FO for pgsql-general@arkaria.postgresql.org; Wed, 18 Oct 2023 14:15:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qt7KQ-004bKD-V2 for pgsql-general@arkaria.postgresql.org; Wed, 18 Oct 2023 14:15:19 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qt7KQ-004bIH-K7 for pgsql-general@lists.postgresql.org; Wed, 18 Oct 2023 14:15:19 +0000 Received: from mail-yw1-x1135.google.com ([2607:f8b0:4864:20::1135]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qt7KO-0016Fh-OL for pgsql-general@lists.postgresql.org; Wed, 18 Oct 2023 14:15:18 +0000 Received: by mail-yw1-x1135.google.com with SMTP id 00721157ae682-5a7c95b8d14so87703657b3.3 for ; Wed, 18 Oct 2023 07:15:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1697638516; x=1698243316; darn=lists.postgresql.org; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=2bKdmAEQ/Mqq+Jt7LgGYKcg6OhhIcuokVoAEzaJAXjA=; b=cMhaq5jXQ0beBjfC8g7pl44bK6Qog2LDNVrjAExsgu6EI28AOqxW+QlPV6N94SRQ/6 T4uR8HwOiGjIHvwCGMEdNpbfeuJ1lHpPtsd25uMW2qDRCsM7d7gahjkdYFQ+Ms5jonNk jbdfMohlvAuSHhTXydsKhZghrW9pp08Cono2WH1sXcN2wpEJNSjoa1iYoHljcpZttvY2 4ghmYDWmSMc1BOzlJ7pFsWcLniSX7xMHAog4lRpqi/h4YuPpVRcEN4p246g8Wjwd2UKy GKDX5zkZYfrl8q2+bpO0MegeAvEqrpAAhbc90wOxyaa2s8P5sBLG641fF9l2fd7UrLO0 eEhg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697638516; x=1698243316; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=2bKdmAEQ/Mqq+Jt7LgGYKcg6OhhIcuokVoAEzaJAXjA=; b=Ddmy/doNKzCyyXQwWPM2miWKrJ6tou4KN9LN0wEdIIVBQ7bMXnH9KycOFLCEpsYGhH 22jxqQuFHsGLxrmuWTM4AJuLncylCC+AtinpG0PpnY+7DLdbKnDGyUNTJXJaJvSswy+c lg0jzGruHu0urFMaKfE4DtrBV+Wpqg5GUqAZnK/k3eiSZczvuBMTZhAU5n9lovjDPeos ysNUb7folkhEEq6xtjPQ53TWOUDpfltzMompOaxIo8LgN7irw/qOGDklnpnLqlP5Oj7O o4XwMLlLK5abU+Kq/l4zbPIVYaBziECdXGMbfa0mjSuvAp5mhH3zZOAyJH3QZvI+W9Pr nb8w== X-Gm-Message-State: AOJu0YxHKWUu3cXe+lmZpvpDBPPqBuDaxzo202Vohuc3vLgkBJHI3Hpw gSJh5WXwwY9ixlaz6lDwmR/Ftg6CyY4= X-Google-Smtp-Source: AGHT+IG73/Ya2bp4gQNSc7xt9Gvn1lq7VGUxVinUKpqAR8AFfTo6wseEtsZiOCL1uzRTkdHiELjwHQ== X-Received: by 2002:a81:4fc4:0:b0:5a8:5824:b953 with SMTP id d187-20020a814fc4000000b005a85824b953mr5662111ywb.8.1697638515797; Wed, 18 Oct 2023 07:15:15 -0700 (PDT) Received: from ?IPV6:2600:1700:bd2c:b810:3d15:81b3:3a0:4d09? ([2600:1700:bd2c:b810:3d15:81b3:3a0:4d09]) by smtp.googlemail.com with ESMTPSA id s189-20020a8182c6000000b005a7bbd713ddsm1513286ywf.108.2023.10.18.07.15.15 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 18 Oct 2023 07:15:15 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------GkflzcN1gx50boiR0XLsh8Ni" Message-ID: Date: Wed, 18 Oct 2023 09:15:15 -0500 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: postgres keeps having blocks 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. --------------GkflzcN1gx50boiR0XLsh8Ni Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 10/18/23 07:40, David G. Johnston wrote: > On Wednesday, October 18, 2023, Shaozhong SHI wrote: > > My postgres is playing up. > > I terminated session that is causing blocks many time. > > New block appears. > > Endless. > > What should I do? > > > PostgreSQL is probably just doing what you told it.  Not possible to give > advice without knowing what you told it to do. You should put more effort > into showing others what your app is doing and how you are debugging it > and the database. > > Killing sessions without changing anything else is unlikely to result in a > change of behavior. That's the definition of insanity... -- Born in Arizona, moved to Babylonia. --------------GkflzcN1gx50boiR0XLsh8Ni Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit On 10/18/23 07:40, David G. Johnston wrote:
On Wednesday, October 18, 2023, Shaozhong SHI <shishaozhong@gmail.com> wrote:
My postgres is playing up.

I terminated session that is causing blocks many time.

New block appears.

Endless.

What should I do?

PostgreSQL is probably just doing what you told it.  Not possible to give advice without knowing what you told it to do. You should put more effort into showing others what your app is doing and how you are debugging it and the database.

Killing sessions without changing anything else is unlikely to result in a change of behavior.

That's the definition of insanity...

--
Born in Arizona, moved to Babylonia.
--------------GkflzcN1gx50boiR0XLsh8Ni--