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 1pLrz8-0000zi-Se for pgsql-general@arkaria.postgresql.org; Sat, 28 Jan 2023 20:39:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pLrz7-0003db-PQ for pgsql-general@arkaria.postgresql.org; Sat, 28 Jan 2023 20:39:37 +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 1pLrz7-0003aM-EQ for pgsql-general@lists.postgresql.org; Sat, 28 Jan 2023 20:39:37 +0000 Received: from mout-u-107.mailbox.org ([80.241.59.207]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pLrz5-0008SU-Jx for pgsql-general@lists.postgresql.org; Sat, 28 Jan 2023 20:39:37 +0000 Received: from smtp102.mailbox.org (unknown [10.196.197.102]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-u-107.mailbox.org (Postfix) with ESMTPS id 4P45sJ2mw8z9sSq; Sat, 28 Jan 2023 21:39:32 +0100 (CET) Date: Sat, 28 Jan 2023 21:39:31 +0100 (CET) From: Erik Wienhold To: Ron , pgsql-general@lists.postgresql.org Message-ID: <1015127885.422245.1674938371999@office.mailbox.org> In-Reply-To: <9864e7fa-27c7-95ac-b9a7-e1ebc4824740@gmail.com> References: <214765350.744944.1674770109151@office.mailbox.org> <9864e7fa-27c7-95ac-b9a7-e1ebc4824740@gmail.com> Subject: Re: Sequence vs UUID MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Priority: 3 Importance: Normal List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 27/01/2023 01:48 CET Ron wrote: > > On 1/26/23 15:55, Erik Wienhold wrote: > > > > There are arguments against sequential PK, e.g. they give away too much= info and > > allow attacks such as forced browsing[2]. The first I can understand: = you may > > not want to reveal the number of users or customers. But access contro= l should > > prevent forced browsing. >=20 > Shouldn't your application layer isolate the users from the database?=C2= =A0 UUIDs=20 > are all over the DBs I manage, but the PKs are all sequences. Yes, I meant the application layer, not Postgres' access control. -- Erik