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 1ttnbc-00H9n0-5X for pgsql-hackers@arkaria.postgresql.org; Sun, 16 Mar 2025 13:00:40 +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 1ttnba-00Do9D-Ms for pgsql-hackers@arkaria.postgresql.org; Sun, 16 Mar 2025 13:00:38 +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 1ttnba-00Do8w-Ck for pgsql-hackers@lists.postgresql.org; Sun, 16 Mar 2025 13:00:38 +0000 Received: from mail-yw1-x112b.google.com ([2607:f8b0:4864:20::112b]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1ttnbY-0039EB-1a for pgsql-hackers@postgresql.org; Sun, 16 Mar 2025 13:00:37 +0000 Received: by mail-yw1-x112b.google.com with SMTP id 00721157ae682-6efe4e3d698so32209977b3.0 for ; Sun, 16 Mar 2025 06:00:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1742130036; x=1742734836; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=rPMr9Sh/4Bp0hQGeWmpW/nRAF+XTlS5QCVhDSdelYd4=; b=KNMrl4vONipDasC/rZOK0mdGYX4aeSqo6D3ka7/m4GtUQ8nmLeuF7sfNGZH2v7uz2E bE40Wu/px6Cb9fDTO9RJL/eS3LbK7zBQ3FNUb20NOlKL5ccI4t9gXrZf0Xi2TDtNHaNX NhU3+6ouyH/57q6LnQFl3MpPtdSITSPjubUQ1Fd9ehsC2L5+zjBtPN+giK5Uyi/FhfpF gZcox7YjWUl4X53R4dUl0esGulZVGDmSldsqjUoR45ppFaphWWrqaEiXA4cn+KlmYD+M Dr1CswLqA89GBQ5dXQ/Si0317NMdUg5vD7c997hOj6k8HAn9zwtAciG/tRSbJypAEqnM ZvEQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1742130036; x=1742734836; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=rPMr9Sh/4Bp0hQGeWmpW/nRAF+XTlS5QCVhDSdelYd4=; b=Qb6S70B73MzIxPQxPUEjOYGrkD5PzDp4TnLi/aOPV36Xlqif4PCGT8xYPWTBnBBGFJ ATOiiumSOb5sf0L2qA3127aE1MZ9QAtrIhqP2wUpPs8OlTY0jVULsmU+lfAYZtDLc1aK SLUhfpqkQsPbnsz17cs8KETr9BGfqlyJPpv7T+cWlb/ZQOjcQjmKb/wucBmklx9p74RW 1GUNR9nRG+WDjRgcmH0NX6vSHFlitmdvP8113qX23WiFvYG5huSeASAPlXSfyRHdqrED g+NSxzqeQr3SedVtkhzGKYJGZCS1+2Jcw75U/nPKZrAAY8t6UMa7SFxDHjFeut1wOPj2 dhBA== X-Forwarded-Encrypted: i=1; AJvYcCV0DT1am8eQiNwLw3XPwRVL2cC/rOCFLkJjnQchqryUtyYpFk4MYp3/UiFDG+vCzpuXLvBlkVo2ZDrA+ygs@postgresql.org X-Gm-Message-State: AOJu0YzcgsAAl/IRZvTwy//HBNEjJAqyP1hAKwinZfEbhaqWttNfG3/R Qp7Jgp/x5k4HpNk8hG8QyJuK7VK0F10uxs8HWt/2UHFrZiEVqmT7xdba1oJUYQnq0VskpWzrouL CXqTn+XdeHPsW/XQwvwtj4oHAML0PY9tgnHerEQ== X-Gm-Gg: ASbGncuqit95W6CO/1cwo6civdKkOzuXrgtRewLr+x6kgeYCE141V2WX7DZ1t9hYmV8 MYISlhiZ8HByBk6sS7Kh/DKUstRTfJKeu6jacbrcJ+DsVHapb7AHItk5gRLr4j1sEpdvo9SgjEJ irH4p7fP3vcuJ88YAidX609rvAMhp1cYrXzpo97J3DMsZigj9VtYmLz0W5qWB2 X-Google-Smtp-Source: AGHT+IGlvhnRHnQ1iqfWz3OozeBoAB04FvztqAfWhnCk2C52E+0v0jQ5H0z4VtoQu7Jrqnc/GvB+oKsgWWuEtr/bXDE= X-Received: by 2002:a05:690c:7006:b0:6fb:1c5a:80f8 with SMTP id 00721157ae682-6ff45f7f483mr106734727b3.15.1742130035901; Sun, 16 Mar 2025 06:00:35 -0700 (PDT) MIME-Version: 1.0 References: <1243984.1739894558@sss.pgh.pa.us> <1246906.1739896202@sss.pgh.pa.us> In-Reply-To: From: vignesh C Date: Sun, 16 Mar 2025 18:30:23 +0530 X-Gm-Features: AQ5f1JpJyD6ulhdxUf_JnbfRg8t5ntNRWyfqFDraP4FQb2cXT7WCwndjSTvKnpA Message-ID: Subject: Re: Clarification on Role Access Rights to Table Indexes To: Nathan Bossart Cc: Ayush Vatsa , Robert Haas , Tom Lane , "David G. Johnston" , PostgreSQL Hackers Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sun, 9 Mar 2025 at 03:27, Nathan Bossart wrote: > > On Sun, Mar 09, 2025 at 03:01:41AM +0530, Ayush Vatsa wrote: > > Maybe we can move ahead with the patch if we can see no other concerns. > > I think we should allow some time in case others want to review the patch. > I do see a concern upthread about increased deadlock risk [0], but your > patch doesn't lock the table, but unless I'm wrong [1] (which is always > possible), it doesn't need to lock it. > > Anyway, here is a tidied up patch. I noticed that Tom Lane's comment from [1] is not addressed. I'm changing the commitfest entry status to Waiting on Author, Please address them and update the status to Needs Review. [1] - https://www.postgresql.org/message-id/279947.1741535285%40sss.pgh.pa.us Regards, Vignesh