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 1sV8Ga-0085qI-5Q for pgsql-hackers@arkaria.postgresql.org; Sat, 20 Jul 2024 11:28:44 +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 1sV8GY-00F5KJ-9A for pgsql-hackers@arkaria.postgresql.org; Sat, 20 Jul 2024 11:28:42 +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 1sV8GX-00F5K9-VK for pgsql-hackers@lists.postgresql.org; Sat, 20 Jul 2024 11:28:42 +0000 Received: from mail-pg1-x533.google.com ([2607:f8b0:4864:20::533]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sV8GV-000Xro-WF for pgsql-hackers@postgresql.org; Sat, 20 Jul 2024 11:28:41 +0000 Received: by mail-pg1-x533.google.com with SMTP id 41be03b00d2f7-7a1215dd114so22745a12.1 for ; Sat, 20 Jul 2024 04:28:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; t=1721474917; x=1722079717; 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=r42c7uW3GdBsn4NpIsybe2nLmahcyP+b4H2pZyG+epI=; b=f8eGBQ05QutJjMJ+x0s0KUj24fRamb1j/sDiZdItQJDa7vcTeZqw08Jz7SePWs2W8f CFUBQrkaQdaRshwlMokM1qPhs0rimH307HH63PQZe0Re+aw2IOKiAohsVrGSIdTuBKL1 MID17PF5gd2kIWjNTMX6gR1AksHGoGjSo01d8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721474917; x=1722079717; 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=r42c7uW3GdBsn4NpIsybe2nLmahcyP+b4H2pZyG+epI=; b=CnWgyL0d3ff86Tpy+MWZHRo0riDJonUsvJl9QcglKWV9HCW2RNO1+Y/4ceICXuqJpQ KfMRibO/3P7i/1wzvMw09kaik3MJRKPwvIQIrXfkiXV06KX4gstdNzo2Sw4AIiMSv3pj aNaXQ9DRP5pUBL+T20rUjkPixTdpA3O0ru3uvYcXHz3iDaEySwCbleAwA3rMTJPiEvtP Rld1aN3cdKdIyP1wXE9DE1sKVfCPkx30Rmdz/2uHCkwYvuOE5r7gfDHZPEzsgxIdmVfN EciftIx+jZjSIG+SeOFnbVEfhS+d31TC24086Ud6OjNfKUoEhn/uJZxqUmKxRZZlAwsT HExA== X-Gm-Message-State: AOJu0YySgNJAUtMJOmbdKmi+iBKhXFBos+1pgYW0KV8bkYFbycAhvOXT h8vDFqfn97803FwRliEKgJOaxXHgTsB2hhOwyTPwb2ZS7hkNMAsoJ01q6Nzxlg== X-Google-Smtp-Source: AGHT+IFx2+/gI8w89Kk5SBVaFd+xukeLDUlJRuY7dPyqBT0TZvC5baTekiz6B8aiSzgxEbCa1eCm0w== X-Received: by 2002:a05:6a20:3d81:b0:1c3:3436:a234 with SMTP id adf61e73a8af0-1c42287f3f7mr3350005637.12.1721474917306; Sat, 20 Jul 2024 04:28:37 -0700 (PDT) Received: from google.com ([2600:1702:a20:5750::48]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-70d14627e4fsm471552b3a.35.2024.07.20.04.28.36 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 20 Jul 2024 04:28:36 -0700 (PDT) Date: Sat, 20 Jul 2024 04:28:35 -0700 From: Noah Misch To: Alexander Lakhin Cc: pgsql-hackers@postgresql.org Subject: Re: race condition in pg_class Message-ID: <20240720112835.f5.nmisch@google.com> References: <20231027232612.99.nmisch@google.com> <20231102030915.d3.nmisch@google.com> <20240512232923.aa.nmisch@google.com> <20240605181706.fe.nmisch@google.com> <20240611024525.9f.nmisch@google.com> <20240614003549.c2.nmisch@google.com> <20240621212842.98.nmisch@google.com> <20240628051353.a0.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 Sat, Jul 20, 2024 at 11:00:00AM +0300, Alexander Lakhin wrote: > 28.06.2024 08:13, Noah Misch wrote: > > Pushed. > > A recent buildfarm test failure [1] showed that the > intra-grant-inplace-db.spec test added with 0844b3968 may fail > on a slow machine > But as the test going to be modified by the inplace110-successors-v8.patch > and the modified test (with all three latest patches applied) passes > reliably in the same conditions, maybe this failure doesn't deserve a > deeper exploration. Agreed. Let's just wait for code review of the actual bug fix, not develop a separate change to stabilize the test. One flake in three weeks is low enough to make that okay. > [1] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=habu&dt=2024-07-18%2003%3A08%3A08