Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r0jAc-007Qw9-25 for pgsql-docs@arkaria.postgresql.org; Wed, 08 Nov 2023 14:04:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1r0jAa-003hVJ-KJ for pgsql-docs@arkaria.postgresql.org; Wed, 08 Nov 2023 14:04:36 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r0jAa-003hUv-8d for pgsql-docs@lists.postgresql.org; Wed, 08 Nov 2023 14:04:36 +0000 Received: from mail-ej1-x62d.google.com ([2a00:1450:4864:20::62d]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1r0jAY-005MPN-0K for pgsql-docs@lists.postgresql.org; Wed, 08 Nov 2023 14:04:35 +0000 Received: by mail-ej1-x62d.google.com with SMTP id a640c23a62f3a-9c2a0725825so1051926166b.2 for ; Wed, 08 Nov 2023 06:04:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20230601.gappssmtp.com; s=20230601; t=1699452272; x=1700057072; darn=lists.postgresql.org; 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=K3DAtnnDgC/2pdr05aFd6IHu62/xidjFwEe9PwPsHd4=; b=f2yeJ9uodDSMa5ZDZLSu+QrDRgEh9UcwlFdYQF9GgV0bMATatj9iuOrKNCpkgIxYQ3 HSCuWFHLjT32xgf4P9XOu3jhphISQNLUZjvlSnw/5hnnGAoCBTawFRnE/NdV0qoPpJs1 Fy/vdmevUatPSkgkhYDh+rgq0HwPd6ahCpLytbXIxMTmNO/mFgWQfOLoGMedkNYLbz8E uKkmJwZ6oiy5Vuq52g+mP92uew5Y84o/4/aO3ErzTcIUit+V+wrpbKcN5y/KPcl8vIV+ 1JfLUv15ETSjlH474zNtFRTeiqr2XUoe4edTYg/fCkRi0pAk5sdLx9LR+VCh1l1RmLRJ XA0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699452273; x=1700057073; 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=K3DAtnnDgC/2pdr05aFd6IHu62/xidjFwEe9PwPsHd4=; b=fmZaNAWhf9XRj06+3vFFee8lpUhW+HPt0IQLP5bz+DFUi2mNt8rp929MLJ33iIkFxd sr5bPAdhg/ri5oYHOLRS/fkzXE9X9QzNUqfgI/tKXWBD/i8Pw2ZKZhPDTPWoGvWiid+O etBjXPI/2u++Kc3uPjJGqzayzBXRCndwRod+oqdOl22PAMSljxJ5ALXkkZ0OfkktOLN1 iOFh8JAang+Eh6lVz2JTffW8XaNlose277gvlVOLgEPDJpkKRYK3CkwPMUA7WKwD0Nho 3ePe5aIfanzHXeWNcgvkvnUoC060X0i/SNCbMi1JVU17HvoZWBDUbPlzvcvpAMs/LOj/ L2zA== X-Gm-Message-State: AOJu0YxjkWu967TCCgx/ENDGo6zGHKKjR0yzir7vpmmfWiAazbatLe6q FmIq4Tp7ZD9rWOEKh3vKIsueqQ== X-Google-Smtp-Source: AGHT+IGSC73cidx/8HhEcOBbAl7JNOGu4EGg81I1gJ2y6SlRbC+x0XY2/ondVvWfNHKiws++0toreQ== X-Received: by 2002:a17:907:a0b:b0:9bf:9c58:e91e with SMTP id bb11-20020a1709070a0b00b009bf9c58e91emr1329036ejc.56.1699452272607; Wed, 08 Nov 2023 06:04:32 -0800 (PST) Received: from localhost.localdomain ([88.116.133.170]) by smtp.gmail.com with ESMTPSA id u24-20020a50d518000000b0053e07fe8d98sm6920365edi.79.2023.11.08.06.04.32 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 08 Nov 2023 06:04:32 -0800 (PST) Message-ID: <4df5fbc8adbe770da13db92bc5cc48f948636640.camel@cybertec.at> Subject: Re: Another user complaint regarding visibility of pg_catalog data From: Laurenz Albe To: "David G. Johnston" Cc: PostgreSQL Documentation Date: Wed, 08 Nov 2023 15:04:31 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, 2023-11-08 at 05:31 -0700, David G. Johnston wrote: > On Wednesday, November 8, 2023, Laurenz Albe w= rote: > > When people ask my "why?", I tend to answer "why not?".=C2=A0 It is not= a security > > problem, in my opinion.=C2=A0 Every user is allowed to know that I have= a table > > "purchase" with a column "credit_card_nr".=C2=A0 As long as the permiss= ions are set > > correctly, that is no problem.=C2=A0 Any attempt to hide that informati= on is at best > > "security by obscurity". >=20 > The typical answer is some variant of trade secrets.=C2=A0 Though wanting= to store > private info in a comment has some merit too. Don't keep your trade secrets in database identifiers or database function = code. But if somebody is nervous about that, they can have their own database. Why share a database with users you don't trust? Yours, Laurenz Albe