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 1pPP3G-0007uf-1i for pgsql-general@arkaria.postgresql.org; Tue, 07 Feb 2023 14:34:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pPP3E-0007KP-Kl for pgsql-general@arkaria.postgresql.org; Tue, 07 Feb 2023 14:34:28 +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 1pPP3E-0007KF-5k for pgsql-general@lists.postgresql.org; Tue, 07 Feb 2023 14:34:28 +0000 Received: from mail-wm1-x32c.google.com ([2a00:1450:4864:20::32c]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pPP3C-0001vt-0C for pgsql-general@postgresql.org; Tue, 07 Feb 2023 14:34:27 +0000 Received: by mail-wm1-x32c.google.com with SMTP id j32-20020a05600c1c2000b003dc4fd6e61dso13311835wms.5 for ; Tue, 07 Feb 2023 06:34:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20210112.gappssmtp.com; s=20210112; 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=8VqvlBWJJMoZGq3YslPBp9YLt+E4CY+Gx+moTBregzk=; b=UudapEQinObzc2iwE9UyHH2rK2PBUiLeOx5kQV+paQwpydWHeqXnoCAXwIExvbGW/x 6WLSmehxYruGSHCdfpHvfeReprEyoJsWd/K7akMvk7z2mwM08/16Ei26iQxkeQpWLsfy 1qiWYSYh/Zo6A0iBOvDqPKREBmiPfm5vktIGeqLLg2NZqwDP1Z2Cs+u/E4q7ua0o69N7 QFqOmbFl9tnl7C/La8aehyOAwmZgQixIwdfYGG0c4uYt/2urAfyXwh6IgZLRvOJuZKKV yVjTsK6AaINMaIVWq19d11bLvpN3bf5yxNFbxYbAesQcCJuXsIiZ3tqE0cyY4WdnO6LX RkKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=8VqvlBWJJMoZGq3YslPBp9YLt+E4CY+Gx+moTBregzk=; b=u1E2gGGAtB9ZfGIJY8e/EmVP4CjyU5ttlgh/ZyduP9PcBBDJkANDa/aFu1r9Vofc/j bN7uVf+l7HyfXWrqsyzgSft3EH+JTg7fw+W30BcZLVIlMQ3shV4Sd0UaFTG3PukOgOi4 T+6LS8RCJOEtyQgb4ngG1kCnWBLDGncX9ZwbnGNiAuMkqqFdrH9Gg9AN/QR1XVzIfn9A I26MAYaogD9iMma0SHca8h0pQBPs5HWUOgU5qKKfafz2R3B0ycngK7wnma2j7cp55mIQ 0MRRrF/D2OSu3XPc3ZS2BQq/b1TdafowKL0dJab9vNGeWjWcDF7ceU2zL4V/R60dHwnT z4Hg== X-Gm-Message-State: AO0yUKV3aKzmOUgRSCF9YtNqxBKPYoo47sXC1qDS0wWchDzPhFUvSns8 HipZwpz3mbdkY+kZgCAs5MqWtA== X-Google-Smtp-Source: AK7set9eZiFQIxiuDm5iJT0AXAtiHnDxklVO8PSZtpqXqPcviVJEshx1GwnQR33Y2fY4qBCaokVRUQ== X-Received: by 2002:a05:600c:3c9c:b0:3dc:d5b:5f6a with SMTP id bg28-20020a05600c3c9c00b003dc0d5b5f6amr3325549wmb.30.1675780465071; Tue, 07 Feb 2023 06:34:25 -0800 (PST) Received: from localhost.localdomain ([88.116.133.170]) by smtp.gmail.com with ESMTPSA id q14-20020a05600c46ce00b003dc47d458cdsm14728127wmo.15.2023.02.07.06.34.24 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 07 Feb 2023 06:34:24 -0800 (PST) Message-ID: Subject: Re: PostgreSQL From: Laurenz Albe To: Joseph Kennedy , Giovanni Biscontini Cc: pgsql-general@postgresql.org Date: Tue, 07 Feb 2023 15:34:23 +0100 In-Reply-To: <81AB3CB7-93E6-4811-9097-5C535FA84BFC@gmail.com> References: <81AB3CB7-93E6-4811-9097-5C535FA84BFC@gmail.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.46.3 (3.46.3-1.fc37) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, 2023-02-07 at 12:36 +0100, Joseph Kennedy wrote: > RLS policy it only affects to command as SELECT, INSERT, UPDATE, DELETE o= r > can affects to operations on whole database, table like vacuum or reindex= etc ? No, that wouldn't make any sense. Row Level Security determines who is allowed to see or create which data. Jobs like removing dead tuples or rebuilding an index have nothing to do with that. Besides, anything that requires the table owner or a superuser cannot be reasonably controlled with row level security, because both the table owner and a superuser are exempt from RLS anyway. Yours, Laurenz Albe