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 1mEZb1-0002SU-H6 for pgsql-sql@arkaria.postgresql.org; Fri, 13 Aug 2021 15:59:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mEZb0-00013d-8B for pgsql-sql@arkaria.postgresql.org; Fri, 13 Aug 2021 15:59:46 +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 1mEZaz-00013V-VR for pgsql-sql@lists.postgresql.org; Fri, 13 Aug 2021 15:59:46 +0000 Received: from mail-ej1-x635.google.com ([2a00:1450:4864:20::635]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mEZax-0001Dl-ML for pgsql-sql@lists.postgresql.org; Fri, 13 Aug 2021 15:59:45 +0000 Received: by mail-ej1-x635.google.com with SMTP id hs10so19250740ejc.0 for ; Fri, 13 Aug 2021 08:59:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:reply-to:from:subject:message-id:disposition-notification-to :date:user-agent:mime-version:content-transfer-encoding :content-language; bh=RKY5B/opVIdcUsYtHdk+bD89yC55k9LV3TcOCXxU7Xo=; b=OdJfJOVIFY4qqLGRkehMs0VjxwT5MX8iNtnPrPK6kkSkQL2UQHgv1Y89CCDxatYI1P K0+CiOSwy91htdEwRgqkubj/E+yfoL6WPY8ufYx6Ck+a93Cz6lmdeYs3YuoqRGkkW4Ib ZJzOk4BcohczcLmNzIC7cJpQoj+778Jt9KvJrcLryyaGvRlFkiyn5MuZMq8MwGng9rZ6 dhmZ0wGNe+5L8uCLUpljgAj5FQmlKZl4ZNevvVeatiYpgZ9F332bPUpHtlKaOyQny8f2 sFCUkq0E5+xAaT8anvuMGrmeJbAsLRXaUHAVNIv7rfjbKfQ5K0S6Mia1j0Fz5/wTA+NR rB9w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:reply-to:from:subject:message-id :disposition-notification-to:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=RKY5B/opVIdcUsYtHdk+bD89yC55k9LV3TcOCXxU7Xo=; b=Ew8Sh32bpcUiMvZM3afhBt1ghf5rEvr0XnZbDWFw5WT4UByx+SWZ/TLJNhrTDWM1Fl b4c94Io+TZfUo30BNR4DmkzmjH4iLpZqiclIubUuKqC+FgiXg8UVzfyut1nO15cwup7J YR34NjEI2nHGYuniX4x1P2pDmY8fLd7SAtAoFU7uLDQ6lLQecltbgl14vtuCbYbqXlOT f3UBJM6i03qLCcVhbQZ0MqknZzlerJCsRMnWsx2eanJ8rk+NVNldwOZ3ER3RsouoXuEj 9q1Ybkt4bxBFobPaCLM9pobeSns7EqxiJg/xnHABV1pI10jHFS7ZOtk3z50eDSGIDQL+ nf+A== X-Gm-Message-State: AOAM532mh3iJ6nbq3dfr9vMOGqjNe4owdqJ3YQjEww23mUt613IWW0wE k6BLHP19R0lOD2aesSbU2vSxWZDtICSetw== X-Google-Smtp-Source: ABdhPJzPJzxEKJhsIcmP39PhNOedT4XY2AgD6PnIVriCPcCtbVvayPk9il7Zr4usLvh00Cw11l9VNA== X-Received: by 2002:a17:906:e0c:: with SMTP id l12mr3189254eji.301.1628870382625; Fri, 13 Aug 2021 08:59:42 -0700 (PDT) Received: from [10.0.0.4] ([41.77.17.12]) by smtp.gmail.com with ESMTPSA id v13sm778499ejh.62.2021.08.13.08.59.41 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 13 Aug 2021 08:59:42 -0700 (PDT) To: pgsql-sql@lists.postgresql.org Reply-To: intmail01@gmail.com From: "intmail01@gmail.com" Subject: How to revoke access and list schema objects Message-ID: <56050f06-8382-07e5-19ce-261cb4ebdffc@gmail.com> Disposition-Notification-To: "intmail01@gmail.com" Date: Fri, 13 Aug 2021 16:00:31 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: fr List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, There are are some people who use my database and I want to prevent them to read code of tables and funtions. I have created a schema in which only postgres user can have access. Other users can not use objects in this but they can list all sql code for each object if they use pgadmin. What is the command to prevent users to list objects and prevent them to read the sql code. Thanks