Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nssAa-0002GZ-Hx for pgsql-hackers@arkaria.postgresql.org; Sun, 22 May 2022 20:27:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nss9Z-0004O2-Fn for pgsql-hackers@arkaria.postgresql.org; Sun, 22 May 2022 20:26:17 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nss9Z-0004Ns-4Z for pgsql-hackers@lists.postgresql.org; Sun, 22 May 2022 20:26:17 +0000 Received: from mail-pf1-x434.google.com ([2607:f8b0:4864:20::434]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nss9U-00060s-LE for pgsql-hackers@postgresql.org; Sun, 22 May 2022 20:26:15 +0000 Received: by mail-pf1-x434.google.com with SMTP id u15so11957211pfi.3 for ; Sun, 22 May 2022 13:26:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=0DXmjCdIGZgVa61ASzXLhCbVCu4O9JFdiP4F9YoyCTA=; b=mZ+i0C1b0gxeePoJoMltKjj0U1eg9HnAoHeO8EOoIAWpWK44f2BMH9wIeYVdN2ztPv rLp0akdDXYfuxvuiR9oERzQa+WDx40U0PLX5+DTBvuDYMZtgtpCbIU6VESV7weG5Lv/L wnLmou8BhkM4K58SvjQAtPctzGbmA8bktT3L8OqnN2xHag/1DhddbeLo+7cP+QZHlB4R 6P2YkrnYLEmeY/25N2/vNBbSfBmlJywwsmKv/OQip4ZW8YC9+SYZPWTt7YSFDxau2HBG vt+KCDUsgPG6RTtJQcrb8HxB0lXekjyQKyMBZVV5Z3SS8X9byJw3b+x0m7vXDhgDph9B kkiA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=0DXmjCdIGZgVa61ASzXLhCbVCu4O9JFdiP4F9YoyCTA=; b=W4fGjO77yd8HoTd/+Y2l5rrxYXV/7tLZ9mMUc8awZslp65VNsaUXQTxIS5VyFyxk0D VpgAb+qV4czfVIDIPwYWOhg3DxQB8IU6gL9HyQ+9XG0/5n+HkgMaRpi0TeB7Ene20BZf EG9ylfw/rH8IGnbI/+Ky8o4b1dIW6d59Rtb1lBS1aIllMW8sikBP6JPzq7BR0dIRmlML MAFgl8TGtahvd9RXBkiVlP26zx8es5ykFQ5lodgUsL8RPdZpenjlWRVG3QvjIe16tTwH 06nIR4+V0bvfMeiqrNOrKfy/d7s7pexsUESunVg0FILhPARLXigEBuQjdjxPO9X6eEvd EdGg== X-Gm-Message-State: AOAM533dwirYy7/rOynOs1Hm9qai7GkCgRTHnNgp/mej5A93WELtoDJ9 JEfPEZAh27dca3ujisbq5f0= X-Google-Smtp-Source: ABdhPJx7chAWALmUFmLXQIntUltWPHBoa5uymWr0bYLVYRyGQFYu2Re8xmLKnMkoiOaH92jcOJgByQ== X-Received: by 2002:a05:6a00:1595:b0:518:a5b2:28d7 with SMTP id u21-20020a056a00159500b00518a5b228d7mr1246262pfk.80.1653251170380; Sun, 22 May 2022 13:26:10 -0700 (PDT) Received: from nathanxps13 ([50.54.155.70]) by smtp.gmail.com with ESMTPSA id g13-20020a17090a67cd00b001df8ddd97ebsm5518643pjm.55.2022.05.22.13.26.09 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 22 May 2022 13:26:09 -0700 (PDT) Date: Sun, 22 May 2022 13:26:08 -0700 From: Nathan Bossart To: Michael Paquier Cc: Ian Lawrence Barwick , pgsql-hackers Subject: Re: docs: mention "pg_read_all_stats" in "track_activities" description Message-ID: <20220522202608.GA892371@nathanxps13> References: <20220520230837.GB877934@nathanxps13> <20220521185743.GA886636@nathanxps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sun, May 22, 2022 at 09:59:47AM +0900, Michael Paquier wrote: > + visible to superusers, roles with privileges of the > + pg_read_all_stats role, and roles with privileges of > + the user owning the session being reported on, so it should not > + represent a security risk. Only superusers and users with the > + appropriate SET privilege can change this setting. > > Regarding the fact that a user can see its own information, the last > part of the description would be right, still a bit confusing perhaps > when it comes to one's own information? Yeah, this crossed my mind. I thought that "superusers, roles with privileges of the pg_read_all_stats_role, roles with privileges of the user owning the session being reported on, and the user owning the session being reported on" might be too long-winded and redundant. But I see your point that it might be a bit confusing. Perhaps it could be trimmed down to something like this: ... superusers, roles with privileges of the pg_read_all_stats role, and roles with privileges of the user owning the session being reported on (including the session owner). -- Nathan Bossart Amazon Web Services: https://aws.amazon.com