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 1qtA9T-00B701-Mw for pgsql-general@arkaria.postgresql.org; Wed, 18 Oct 2023 17:16:11 +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 1qtA9Q-006jbN-Sa for pgsql-general@arkaria.postgresql.org; Wed, 18 Oct 2023 17:16:09 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qtA9Q-006jbF-Hk for pgsql-general@lists.postgresql.org; Wed, 18 Oct 2023 17:16:09 +0000 Received: from mail-pg1-x535.google.com ([2607:f8b0:4864:20::535]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qtA9L-001Ooz-6v for pgsql-general@lists.postgresql.org; Wed, 18 Oct 2023 17:16:08 +0000 Received: by mail-pg1-x535.google.com with SMTP id 41be03b00d2f7-5b837db1b26so435957a12.3 for ; Wed, 18 Oct 2023 10:16:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1697649361; x=1698254161; darn=lists.postgresql.org; h=content-transfer-encoding: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=ohbWEdFWXp4b5pIg7gSgB8/64iFoylP6G0dJ/O6FwZ4=; b=YsW0DW8us2GwuGmJipCuP+MgZBbQXNUOI4irrxSIeQZdm0LUvHlZOONKmpm1Pssg2O tq5pd9wsWgxfLQR2EmjxB8GsKCrTtpjLtePnJoJL26LL2ZRAvYuK5C9+AOZCIO0jH2xW TkzGYFEgJbPIfxhh1KRc0HzOU/quvC8SO29Yr/brETKyhjg0ONvde/fgw+4Ma6CfTQfS EKyom4m0FrlJEnz1bOP27RN1VFwHegNTirXJnEo/wzG1fiUYAIvSuIuPvDdzsXyQ/bZC 3R5ysKuVWEs7YykxoCjCX2sicoD3iFsuUvVjPOvucw6BghP4n+sQhAVwm7A+9cMPaVv2 iirA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697649361; x=1698254161; h=content-transfer-encoding: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=ohbWEdFWXp4b5pIg7gSgB8/64iFoylP6G0dJ/O6FwZ4=; b=TgpnwlBSAApVL1cN559VRP5iYqUcZAXl4ipDj+eq9Dz/B1HP49WgAPkNuGSM3N0CYy lULGFPQiIcPL2IcPZSjDrqVT1SNSeGOb2+6umFkPYqAheEZfqoPIgPh72KF3hJc89Cvc 6y4CMs8SGVBJ5w85piLvwNu5kvKq6Uv/xuYAqntGdMyQ22/oCloCMM5CNkIVI4UHyq/0 yMaOysk0bpAenj5ZTYOKG1OlbPiSahZS3gF3JRcFqISCdHVE9mMJP+qxPXwb0ZXJYQzn g6F42p4Ay+EiqWgQ/O2+gn2FkSkXqD2Mt5f8M1+LxoxHwfiCDIt7FET63au/VQalYS7q +cLg== X-Gm-Message-State: AOJu0YxTeIUIyNmJnT+8hyXuSQ6h4iWIvn9ZcXniFrHIK+qIeO9WfXCh 8fpbaFzPOQCgmHccWvGmBhKnlUThQfx6PA== X-Google-Smtp-Source: AGHT+IE68FhO31bpIs8u9JHlbj9Tf7nGr0ixZaEWaYCYTgr6cOXyS3HDWt4Uri7X+07skQO9F5GEvA== X-Received: by 2002:a17:90a:356:b0:27d:2054:27b1 with SMTP id 22-20020a17090a035600b0027d205427b1mr6018223pjf.32.1697649361331; Wed, 18 Oct 2023 10:16:01 -0700 (PDT) Received: from [10.128.56.52] ([155.98.131.4]) by smtp.gmail.com with ESMTPSA id gl12-20020a17090b120c00b00274a9f8e82asm158719pjb.51.2023.10.18.10.16.00 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 18 Oct 2023 10:16:00 -0700 (PDT) Message-ID: Date: Wed, 18 Oct 2023 11:15:58 -0600 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: postgres keeps having blocks Content-Language: en-CA To: pgsql-general@lists.postgresql.org References: <8c83acd0-85af-4d1e-916a-304a4bf6ac81@aklaver.com> From: Rob Sargent In-Reply-To: <8c83acd0-85af-4d1e-916a-304a4bf6ac81@aklaver.com> 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 10/18/23 10:15, Adrian Klaver wrote: > On 10/18/23 04:27, 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? > > Provide more information. > > 1) Postgres version. > > 2) Define what blocks means. > > 3) Show us the statements/code that is causing the issue. > > 4) Post relevant sections from the Postgres log. > > Commit your transactions?