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 1meqiA-0000Rj-9c for pgsql-hackers@arkaria.postgresql.org; Mon, 25 Oct 2021 03:31:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1meqi9-0005yo-8M for pgsql-hackers@arkaria.postgresql.org; Mon, 25 Oct 2021 03:31:45 +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 1meqi8-0005yf-SA for pgsql-hackers@lists.postgresql.org; Mon, 25 Oct 2021 03:31:45 +0000 Received: from mail-pg1-x533.google.com ([2607:f8b0:4864:20::533]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1meqi6-0004Vr-E4 for pgsql-hackers@postgresql.org; Mon, 25 Oct 2021 03:31:44 +0000 Received: by mail-pg1-x533.google.com with SMTP id h193so9561320pgc.1 for ; Sun, 24 Oct 2021 20:31:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=j-davis-com.20210112.gappssmtp.com; s=20210112; h=message-id:subject:from:to:cc:date:in-reply-to:references :mime-version:content-transfer-encoding; bh=waHKGBOTuRwn3rwDGvrjQ93OuNr0SFfW2aXAmVXVqjw=; b=7U/CoRPaTKl/8WQ46Klst3Ko9RK0aaSyCAhwIee6zCRx/AsGoLVs3QJ9Dc174/9Art Dbgkv1hV2R58B5/9RcDIl7NnJR3EjYZ7Q9CTkgjigtAxGZLXrS1+t6zf491aaU9o6WJV cjTeQa3G5jyfiBZBsU/2wIzLVSu9Ykl+b9gC4m9X7ecJ7e9MrsHnLSBh6nK1bfBomWEb bjKofLt/Sk32b+nguO6XM2E4rDmLfM8sMyuiFjJBFX7Fkwkk9L+xMTBuTOxDohk2593s KfQ2S9gP0ZuIkuEamy95ymJ5kSFLV2TFJYrtU3+EVkcmdwDK4cWIy3fFMBGegRGKvIvT BOsQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:mime-version:content-transfer-encoding; bh=waHKGBOTuRwn3rwDGvrjQ93OuNr0SFfW2aXAmVXVqjw=; b=Lz1QpdqBdJYeg/o1S/5RA9U3TrWT2rxLZSL2hdkK2cCQ7JPEfjqGjBSP9Eu4qF8jDm E82k7oCuNMbJAcox3KG0me0UfW/jM8U7JiFKLAWlthEY/zTFcCEvGAi5XSu17BRPgyHT c3tX3Lwqf8IFRHPfNN1OiFJv86MaEsm25d+6IrlbbUpLIjJ6Ya4zFeNaipk8v98k1tza dX4LTzmUl6rfdLBzX6DCuDBwYeHPBkn+U9irw7McHdf+F4S4ZXrZtyuM2P5STSH7uEER LEHZlx3yuoQn2vp5DXlpD6byj65lXCVWpFBPQ0QLEYXLpMSvOaoh2QrgFYfIpPBWG9f7 tH1Q== X-Gm-Message-State: AOAM530L4tIMCz9Rq379fXQO/0/vmF8cWByICyXXPJAcbBfeiithZJYu Om6yXGOksKiLRMAHLhUj49P5/8IGDhU= X-Google-Smtp-Source: ABdhPJwnwqzNdTiOQajzAyqH7MBH4z4/KuzSsOqni6/24xQLBZeGI1zqGWlPVaSdRhXuIbT2AstidQ== X-Received: by 2002:a63:3c48:: with SMTP id i8mr11522048pgn.404.1635132700051; Sun, 24 Oct 2021 20:31:40 -0700 (PDT) Received: from jdavis.lan (c-73-231-146-4.hsd1.ca.comcast.net. [73.231.146.4]) by smtp.gmail.com with ESMTPSA id v22sm17387117pff.93.2021.10.24.20.31.38 (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Sun, 24 Oct 2021 20:31:39 -0700 (PDT) Message-ID: Subject: Re: Allow pg_signal_backend members to use pg_log_backend_memory_stats(). From: Jeff Davis To: Kyotaro Horiguchi Cc: bossartn@amazon.com, pgsql-hackers@postgresql.org Date: Sun, 24 Oct 2021 20:31:37 -0700 In-Reply-To: <20211025.115333.563958443822411952.horikyota.ntt@gmail.com> References: <33F34F0C-BB16-48DE-B125-95D340A54AE8@amazon.com> <20211025.115333.563958443822411952.horikyota.ntt@gmail.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5-0ubuntu0.18.04.2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, 2021-10-25 at 11:53 +0900, Kyotaro Horiguchi wrote: > In other words, I don't think pg_signal_backends is not meant to > control "log something on another session" or "rotate log file". > It's > danger that if we allow somewone to rotate log files, that means to > allow same user to terminate another session. The current patch doesn't allow members of pg_signal_backend to rotate the log file. Do you think pg_signal_backend is the wrong group to allow usage of pg_log_backend_memory_contexts()? Alternatively, it could simply not GRANT anything, and leave that up to the administrator to choose who can use it. Regards, Jeff Davis