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 1v7HtX-000Of9-1a for pgsql-hackers@arkaria.postgresql.org; Fri, 10 Oct 2025 18:31: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 1v7HtU-00DifC-Pn for pgsql-hackers@arkaria.postgresql.org; Fri, 10 Oct 2025 18:31:09 +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 1v7HtU-00Dif4-Fr for pgsql-hackers@lists.postgresql.org; Fri, 10 Oct 2025 18:31:09 +0000 Received: from mail-pg1-x529.google.com ([2607:f8b0:4864:20::529]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1v7HtT-0014ze-1W for pgsql-hackers@postgresql.org; Fri, 10 Oct 2025 18:31:08 +0000 Received: by mail-pg1-x529.google.com with SMTP id 41be03b00d2f7-b5f2c1a7e48so1590874a12.0 for ; Fri, 10 Oct 2025 11:31:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=j-davis-com.20230601.gappssmtp.com; s=20230601; t=1760121065; x=1760725865; darn=postgresql.org; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:from:to:cc:subject :date:message-id:reply-to; bh=xenSGoXcu/zlsTQgGwmqXqL8d4TRynFxSrJ/ootoaxw=; b=YjHSjpqDrTqHD0UNKlOdE4PGWErcpdRBLhdn14+DAKMiTsY9JvR8Vck6BSAknqJoM1 p1Jx/JtzKXo3fAJAsA/r0U/tLTWgEkhAqwqDFnS9dOoJciVx0MiQ6sH/75Ykwb7RSFSt zjokXjJqi85QOlK5dfy0CI70RbiZHsriMfZTYBAPGSbEsd4j/4GAZGTeBBtzaE2M5OHq +/D1JJ4Cq9zgcPlrmklKzdkLyMc8ECV8wvvVOvWhPcQkLTueARzDhZ8XQjZwA3ikjU5h ffchr5vjgkFkVTzwtlOGEJ+1VU3HctUZ264b5NiFY98CvH846KJlkJgfemUy+GDOMq8+ G24A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1760121065; x=1760725865; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=xenSGoXcu/zlsTQgGwmqXqL8d4TRynFxSrJ/ootoaxw=; b=qW/WSMxYOf2G28pG2H95UOlZrMSWcEHMZjonHJqBZSKHvXZAx3cmFfeR1bcL5BWdGM SsH1VbLEB69jAP5iho3AzJpp0Nh+dG3T4iPmzqPFS2hIMpp17IfuQQdES9ySGqgeQjlI fVjabTTLK5sXSuwUOG9+5gS+E6bcfuDjauwLQVdk0ti0prorPDwGKQwgR9FYwrBd0KCJ CGaEb1lcBaX81kwwyrqdfEWUoVq0Dgj2D0Yej+k5BhjZNL3HBw80gwKSqL36Bzqw2a7d RiPYZpH12N5MXmU2t2XP+4tKRDlzfGT7gxGrm2UvNoOxxCaH16bs/OphGiOkOPBn5bFa 1dxw== X-Forwarded-Encrypted: i=1; AJvYcCWY9x+lbD//j0B3m5Dj/wdoNH9QKGUMQsCB2oMvP+VZZfxFt/Pbxn6nsK0bHzlKsIWNHGgkGgkCX3nJ/M1t@postgresql.org X-Gm-Message-State: AOJu0Ywixob5O9ZIHFXxHVeoeDLUZo/Skx4zM7/EFvsO1ECJQmEyO/vD l2e2HSZNhiyNmZaR2B8KNpbUDrM3/Kt09vAHCsA/VNH7tkq4k/pxqjVOLoFNLGjZjg== X-Gm-Gg: ASbGncs7+SLX0KDqRMdZBYfzsa44gFwCMLAUBAC7vaA2UFJhz8F+Ze0YosjQtarES0Q BnObdtc4FaqvlKeBGxbmBd8IMlgsRvSIwlD3IUsH2cXIZkF/JizjxGXFpv2nO6WwaWcWDbxN7ll qGBSaNeSPjTI1gC8HJov9G6+AfVp9H7RN7tRHCa/Pp1cdILSxqYJyMpcO1dAo4gOj7TyEfbyhN6 V0vojhRClBjcnrREIEGpoN3dD+6feZHThIzzzdXvLg+9TJmIFhZPSS/5sKLzSpXArfuzYAJrxPP loYqPEvD0/fzZnkembjGgkvqV1OUSwE7J1GM4s8l4yHB1LcQW1K8bD8srRaQ5rvKqFXXopjeLTh /3RF8TBK/JEgbMAqOLJcfry4I/ed3+dm9eUTb0PfuF9sPa7pYYc6Kq7RFvKSg9UgVh3xXBvsLuy WFN9kFi85a X-Google-Smtp-Source: AGHT+IGv1GAvKj7NA3FoZI0w81W1uiQsB5sDiTDNqfJcJ98OYzEO6CWstrZ+AUP2PQpFP4o1xDgQrQ== X-Received: by 2002:a17:903:2381:b0:269:aecc:a454 with SMTP id d9443c01a7336-290272903bcmr167790315ad.11.1760121064865; Fri, 10 Oct 2025 11:31:04 -0700 (PDT) Received: from jeff-ws-bridge.lan (c-24-7-19-3.hsd1.ca.comcast.net. [24.7.19.3]) by smtp.gmail.com with ESMTPSA id d9443c01a7336-29034e175f3sm63370505ad.29.2025.10.10.11.31.03 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 10 Oct 2025 11:31:04 -0700 (PDT) Message-ID: <31a67adbb10b85ff7cddeafe75b9f6505c902e57.camel@j-davis.com> Subject: Re: Clarification on Role Access Rights to Table Indexes From: Jeff Davis To: Nathan Bossart Cc: Tom Lane , Ayush Vatsa , Robert Haas , "David G. Johnston" , PostgreSQL Hackers Date: Fri, 10 Oct 2025 11:31:03 -0700 In-Reply-To: References: <279947.1741535285@sss.pgh.pa.us> <3432170.1758730414@sss.pgh.pa.us> <8af53c6e8992aa706e63aafe60a3bcf100b524d1.camel@j-davis.com> <7b0e2774cdcc8f522ac82f64a8d7266f353a5094.camel@j-davis.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.52.3-0ubuntu1 MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, 2025-10-10 at 11:26 -0500, Nathan Bossart wrote: > On Thu, Oct 09, 2025 at 04:18:03PM -0500, Nathan Bossart wrote: > > There's a similar pattern in get_rel_from_relname() in dblink.c, > > which also > > seems to only be used with an AccessShareLock (like pg_prewarm).=C2=A0 > > My best > > guess from reading lots of code, commit messages, and old e-mails > > in the > > archives is that the original check-privileges-before-locking work > > was > > never completed. Interesting, thank you for the analysis. > > I'm currently leaning towards continuing with v4 of the patch set.=C2= =A0 > > 0001 > > and 0003 are a little weird in that a concurrent change could lead > > to a > > "could not find parent table" ERROR, but IIUC that is an extremely > > remote > > possibility. >=20 > After sleeping on it, I still think this is the right call.=C2=A0 In any > case, > I've spent way too much time on this stuff, so I plan to commit the > attached soon. I'm OK with that. v5-0001 is an improvement over the current situation. Regards, Jeff Davis