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 1pRJcb-0000TC-8Y for pgsql-general@arkaria.postgresql.org; Sun, 12 Feb 2023 21:10:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pRJcZ-0005qP-Mp for pgsql-general@arkaria.postgresql.org; Sun, 12 Feb 2023 21:10:51 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pRJcZ-0005qE-CB for pgsql-general@lists.postgresql.org; Sun, 12 Feb 2023 21:10:51 +0000 Received: from mta13.doruk.net.tr ([81.21.172.170]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pRJcT-0001Xn-W1 for pgsql-general@lists.postgresql.org; Sun, 12 Feb 2023 21:10:50 +0000 Received: from cmail19.webkontrol.doruk.net.tr ([212.58.6.99]:58438) by mta13.doruk.net.tr with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pRJcP-000FMq-Il for pgsql-general@lists.postgresql.org; Mon, 13 Feb 2023 00:10:41 +0300 Received: from DESKTOPQCEPGF2 ([176.88.190.218]) by cmail19.webkontrol.doruk.net.tr (12.2.1 build 1 ) with ASMTP id 202302130010382230; Mon, 13 Feb 2023 00:10:38 +0300 From: To: Cc: Subject: Re: pg_dump problem with postgres user Date: Mon, 13 Feb 2023 00:10:38 +0300 Message-ID: <001601d93f26$75663540$60329fc0$@1nar.com.tr> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Content-Language: en-us Thread-Index: Adk/JQ4j0mQrAwWFS3WaCETDSUe3gQ== List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hello, My service provider spam filter just blocked your message and so I send a separate one. Your suspicion seems like correct. Postgres user is no more a superuser. Seems like they added postgresql_user and made it superuser. I thought I only allow access with certificate to the database. OS access is limited to single IP. Probably this is the weak point. I should read more about security in general. postgres=> \du+ List of roles Role name | Attributes | Member of | Description -----------------+-------------------------------------------------+-------- ---+------------- postgres | Create role, Create DB, Replication, Bypass RLS | {} | postgresql_user | Superuser | {} | postgres=> Is it possible to put everything back to normal? Can I use single user mode to change passwords and permissions? Thanks & Regards, Ertan