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 1sHqxr-00BDGk-Os for pgsql-hackers@arkaria.postgresql.org; Thu, 13 Jun 2024 20:22:31 +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 1sHqxp-007NLt-LJ for pgsql-hackers@arkaria.postgresql.org; Thu, 13 Jun 2024 20:22:30 +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 1sHqxp-007NLC-3z for pgsql-hackers@lists.postgresql.org; Thu, 13 Jun 2024 20:22:30 +0000 Received: from mail-yw1-x1133.google.com ([2607:f8b0:4864:20::1133]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sHqxn-001AqJ-Dt for pgsql-hackers@postgresql.org; Thu, 13 Jun 2024 20:22:28 +0000 Received: by mail-yw1-x1133.google.com with SMTP id 00721157ae682-631458848b3so11863197b3.3 for ; Thu, 13 Jun 2024 13:22:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; t=1718310146; x=1718914946; 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=kPqALAWQeABOeGYZLCjwHV7Lw65JMw2VImwo+T7nLuk=; b=ODc2AK5PdM90WERw2Jz/gcHjK9IElbPt6Uj0kHEwoZbpAcJ7vPLwLBy7D278Ua8ChW j2/ElLVBklLOX6cFhbmAtQMUi26cI8w6D9Prs3g+mmJCeJ8L7Sh6CbfOtEaNX1d72fi+ AJKh0f7bDobJ2xLWqiy4NuM+2HxeyTJMobFi8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718310146; x=1718914946; 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=kPqALAWQeABOeGYZLCjwHV7Lw65JMw2VImwo+T7nLuk=; b=bZHhO3HCwRVMUstuG72DR1DCRcBbfoVf0krc7L0oWdgLWOouzA9ifjzpKYDuJrhFKi LR6aPezcEdKxA46Ld+TNlK6l6J+i4M1nRNWKrLfdYPAYMyETIK24L7kKAHdiWQlb3rT+ vIMb9wqgpfJ6/CFCIAeWlgqsNr8aFwGiTdCAime+hvJudOFBt329/xK9ySZL5dpu6r0k tMgVNxFld3bJmqi/NFiOCFmyLHO6gVQhJg9dAb4KZ23jUsOHdXbYBEe1OlWBJYTQi2Uw Cg1mJlEywLv2ZA71aISD9qMO2VcmR03jjcFq2E2Xy9wqPur4llfGCcp5KSPcmBd72Y3H jv0A== X-Forwarded-Encrypted: i=1; AJvYcCWZOgpRBDibmFkEyrv1zB56pbaj90ivCRftJOIKpMZHW7cGKC0G/qE3xf53rQaUzi9btyKoQzDWgQkyEhBrdEhV4QXKRatLEY36NjL2 X-Gm-Message-State: AOJu0YxhiWR5HU+ClEpogb7VwkLtUiHz8e3nLGveoU3j8jLM3JfxXNJ/ ovEyYHanQ6wzhiQ/q+Bop8tG6Lc8ya5w1wgTERQAXRg/z3ru6UMtWLw706xSnQ== X-Google-Smtp-Source: AGHT+IEQCmJJoaD29jmus3afaTRWi3DgzRhgBWhiaM+r3lG5AgLntDXpdoDRDH7olaxJOObiOWB2EA== X-Received: by 2002:a0d:dd43:0:b0:62c:c670:8010 with SMTP id 00721157ae682-632247103f7mr5954327b3.35.1718310146473; Thu, 13 Jun 2024 13:22:26 -0700 (PDT) Received: from google.com ([2600:1702:a20:5750::48]) by smtp.gmail.com with ESMTPSA id 00721157ae682-631183d78e5sm2726367b3.22.2024.06.13.13.22.25 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 13 Jun 2024 13:22:25 -0700 (PDT) Date: Thu, 13 Jun 2024 13:22:23 -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: <20240613202223.11.nmisch@google.com> References: <20240512232923.aa.nmisch@google.com> <20240605181706.fe.nmisch@google.com> <20240611021927.30.nmisch@google.com> <20240612194857.1c.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 10:02:00PM +0200, Michail Nikolaev wrote: > > 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. > > I was guided by the following logic: > * A pg_class race condition can cause table indexes to look stale. > * REINDEX updates indexes > * errors can be explained by different backends using different arbiter > indexes Got it. The race condition of $SUBJECT involves inplace updates, and the wrong content becomes permanent. Hence, I suspect they're unrelated.