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 1sHTy1-0084hw-CM for pgsql-hackers@arkaria.postgresql.org; Wed, 12 Jun 2024 19:49:09 +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 1sHTxy-00673i-86 for pgsql-hackers@arkaria.postgresql.org; Wed, 12 Jun 2024 19:49:07 +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 1sHTxx-00673a-Un for pgsql-hackers@lists.postgresql.org; Wed, 12 Jun 2024 19:49:06 +0000 Received: from mail-yw1-x112e.google.com ([2607:f8b0:4864:20::112e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sHTxw-001KuY-10 for pgsql-hackers@postgresql.org; Wed, 12 Jun 2024 19:49:06 +0000 Received: by mail-yw1-x112e.google.com with SMTP id 00721157ae682-62ceb6a4e97so3147617b3.1 for ; Wed, 12 Jun 2024 12:49:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; t=1718221742; x=1718826542; darn=postgresql.org; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=WR+oxxSgwQ4T/9vpnDcqw3sVs3+YlF5o15KEvWamSSE=; b=TYkOPagbuWcx/Vz8sv7oAlfK3ghZ9C9G2/L6GFeJgtqg8u9+1tHPDjpgTaEn4/UNeg /rjXsAdOW+bw03PvtwresNUmqQ5C1nhREG8Roqcp79UXmVZRX9khCeioC1tYvwgiio+V IijVd9272ax9wrjjammv5y6SKcE3nXGe4wfz4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718221742; x=1718826542; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=WR+oxxSgwQ4T/9vpnDcqw3sVs3+YlF5o15KEvWamSSE=; b=MEJ77AWl7ueD0H9NpHkoDP4DW8NRwtjMv1KjyD6Fi3Ul0vKyTgZYHkGLTNxrUVPjsS 0PDHSLoD7gXcicXQwjVvRstaVQSwjnb7FJTrY2CAyXtKuxNM9XckncvOmdiLiMvc6sAc LiI3iXUrSBcsVQB1hvWEyeLtdiEbYlrRblQqbozmvoamdT5JE88zM/qIWzKmtK0HSui5 gPMQQLt5eRQmZKK9aTBz3sluJHL3OHRUue0QJv/NUHlFD2SZ0nreCuYddHDpTF44e9cp 9KDWKHvPPAMs6cwvmAXaAvq/qv+JUqVp9izCOShABvNalNfqdvlgQ4JJIDyVh0SG9y6a YzLw== X-Forwarded-Encrypted: i=1; AJvYcCUwV0h9HZ7HNFMrE9TmJLi7KbjhaJ1TxiJVsPQfMsLLCiFr9stk0wEtW5XDMnvwGawzhznHTQVBlNn6ll7GjiMwXab2dpCgBbNKRyDz X-Gm-Message-State: AOJu0YwTI46NSGpruuoHJkh3WaPR7IFpx8cFswPfMm7L7mWUeQlnhsB+ oVwRoClU2CRT4DgLuGY9wBr+qq2p0gI4dPnlrIefYaQADfd+jII+GjKaBhysuA== X-Google-Smtp-Source: AGHT+IHxoUzH6ksCIcYOqwMI49yCTWBGxV0eZkCDXpYrXxT8HdmYaMNfhFqsZ6hNxCM8pxoiH9euMg== X-Received: by 2002:a0d:df06:0:b0:61b:bd7f:c62b with SMTP id 00721157ae682-62fbb8ee7f1mr27034277b3.2.1718221740717; Wed, 12 Jun 2024 12:49:00 -0700 (PDT) Received: from google.com ([2600:1702:a20:5750::48]) by smtp.gmail.com with ESMTPSA id 00721157ae682-62d0a541d29sm12463587b3.2.2024.06.12.12.48.59 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 12 Jun 2024 12:49:00 -0700 (PDT) Date: Wed, 12 Jun 2024 12:48:57 -0700 From: Noah Misch To: Michail Nikolaev Cc: Michael Paquier , Robert Haas , pgsql-hackers@postgresql.org, Tom Lane , Smolkin Grigory Subject: Re: race condition in pg_class Message-ID: <20240612194857.1c.nmisch@google.com> References: <20231027232612.99.nmisch@google.com> <20231102030915.d3.nmisch@google.com> <20240512232923.aa.nmisch@google.com> <20240605181706.fe.nmisch@google.com> <20240611021927.30.nmisch@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/2.2.12 (2023-09-09) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, Jun 12, 2024 at 03:02:43PM +0200, Michail Nikolaev wrote: > I am not sure, but I think that issue may be related to the issue described > in > https://www.postgresql.org/message-id/CANtu0ojXmqjmEzp-%3DaJSxjsdE76iAsRgHBoK0QtYHimb_mEfsg%40mail.gmail.com > > It looks like REINDEX CONCURRENTLY could interfere with ON CONFLICT UPDATE > in some strange way. Can you say more about the connection you see between $SUBJECT and that? That looks like a valid report of an important bug, but I'm not following the potential relationship to $SUBJECT. On your other thread, it would be useful to see stack traces from the high-CPU processes once the live lock has ended all query completion.