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 1pPPFH-0008Ui-U1 for pgsql-general@arkaria.postgresql.org; Tue, 07 Feb 2023 14:46:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pPPFG-000531-Hk for pgsql-general@arkaria.postgresql.org; Tue, 07 Feb 2023 14:46:54 +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 1pPPFG-00052r-52 for pgsql-general@lists.postgresql.org; Tue, 07 Feb 2023 14:46:54 +0000 Received: from mail-wm1-x32b.google.com ([2a00:1450:4864:20::32b]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pPPFE-00024T-1M for pgsql-general@postgresql.org; Tue, 07 Feb 2023 14:46:53 +0000 Received: by mail-wm1-x32b.google.com with SMTP id k8-20020a05600c1c8800b003dc57ea0dfeso13370090wms.0 for ; Tue, 07 Feb 2023 06:46:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=136oiHonoQRAqVTRC6spkYDoVekSoP4qTdBnLgjTNFM=; b=NxMEa+3UlBsUXsCRCGNrl7ntpSXKG+1chYaw9sRyTNIocWCgvmO7asTb1o9ulm06xN 4zVa2ZTZ6icomf63gB0m3etKq91m1m9pJc7E9huYXrDboHvLMCmrry+j1JcdmFzHXZR7 Z3+HY/OVEFNlw+ANhIR8Kfu++5JA3SgfEORd0IZt+ppPYZU251P6+AaK7POaMtczlsoL xcPq6opC8O/3wSamhOgalrkvCLBVIueKY0M5ocZcId5NzkqlVVUduAlPV2hQ2OZcOE74 NcHRsutumu/KC5rTRgBcYN01vbItwUjjEB/MadRDOYgVorHhUBPbfH6iJf51q2+TSIV/ nx4A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=136oiHonoQRAqVTRC6spkYDoVekSoP4qTdBnLgjTNFM=; b=qgvK22mJhfCkP+ArkERbmvM7zU3J1xg/gpYTWxSn3iVFlAGhOdvINSnxjvyRVYQcVn 2PTdG+t+qM65VQI9BOFTsfyz/m4tkbRjeL7I3p+1kQngIGIXdZx3efsbHr+91lbrY4Vr 0LW2/0UMTZ3k7/6XxRzvLd7kFUBICcx31kQhRatC/KwfHAxG0VBnSNz7RwVepwxd0spj 19UvS3AjaS6P501mtodKZtHNlOXxCgT2l5OJ/+R6hpaFoPbVQXeqSgfVLqhU+KuN45Xw Eu0dI75yhRmJRXZdzYf84vgwAkLV12zS1UYCWiGYbnt/yADtQKBMYma0miUVny+fK666 7RaQ== X-Gm-Message-State: AO0yUKVVhGF+QC4rfQjcg7PJbZ00uPb7aBhs8hSAfWbzk05N9+LzghEx NXtI03EuJvyfbffcjo+n6HZe5+SLPzo= X-Google-Smtp-Source: AK7set83HONT+3dgHOnCAomR2W+j0ofRO3mr/p5rxzeUlZo2FbdtAJpmktOLRKxnsmeLQEYN978V3w== X-Received: by 2002:a05:600c:4f8e:b0:3df:f2a5:49e0 with SMTP id n14-20020a05600c4f8e00b003dff2a549e0mr3565784wmq.40.1675781210984; Tue, 07 Feb 2023 06:46:50 -0800 (PST) Received: from smtpclient.apple ([185.170.224.189]) by smtp.gmail.com with ESMTPSA id q9-20020a1ce909000000b003dc34edacf8sm18813050wmc.31.2023.02.07.06.46.49 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 07 Feb 2023 06:46:50 -0800 (PST) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: Joseph Kennedy Mime-Version: 1.0 (1.0) Subject: Re: PostgreSQL Date: Tue, 7 Feb 2023 15:46:39 +0100 Message-Id: <8C7CE513-7187-428E-81C2-508C85812B54@gmail.com> References: Cc: Giovanni Biscontini , pgsql-general@postgresql.org In-Reply-To: To: Laurenz Albe X-Mailer: iPhone Mail (20D47) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Thank you Laurenz, I just wanted to make sure.=20 Do you know any alternative solution to RLS ? > Wiadomo=C5=9B=C4=87 napisana przez Laurenz Albe = w dniu 07.02.2023, o godz. 15:34: >=20 > =EF=BB=BFOn 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 ? >=20 > 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. >=20 > 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. >=20 > Yours, > Laurenz Albe