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 1pRJgr-0000et-7n for pgsql-general@arkaria.postgresql.org; Sun, 12 Feb 2023 21:15:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pRJgq-0005or-4V for pgsql-general@arkaria.postgresql.org; Sun, 12 Feb 2023 21:15:16 +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 1pRJgo-0005oh-FY for pgsql-general@lists.postgresql.org; Sun, 12 Feb 2023 21:15:15 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pRJgk-0000Zl-OJ for pgsql-general@lists.postgresql.org; Sun, 12 Feb 2023 21:15:14 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 4E0AE5C00A6; Sun, 12 Feb 2023 16:15:07 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Sun, 12 Feb 2023 16:15:07 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm3; t=1676236507; x= 1676322907; bh=+jXWUT7EMf0B4zewxAqCj65WVbcF7UHLooFm7fezkgc=; b=q 8xkLdc5BK9nvdF+6gLPJd3YpxdkmgS1CTwumJW47QfPmxBQpfnm4DKhWmf4q/D/o QSA6nVK1J0M8PQOYefpZuwDRYMPlqWFAHUh2pcr9wvRJlmYVVAWL0dPguzxglfzw 6jA/dqlM+ZvZJMjN119fUJqWptr5DvDNtI9eyNSEdh9HJegw/DMpneKuefmF7NAL s7K29Zdfwr888CmXJ0DvACSvYITm2AKOQflYXMCaEfJZVtwBg89CD5AY2eEMeVF5 5GgdAiRdXio13/yYP/ZEXL6OYHf8QFC0sNg92GVhaq0+GGrU6NFUw1BQh/iYDoCn mFxkNeTnXsAqKYyDkj3hQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1676236507; x= 1676322907; bh=+jXWUT7EMf0B4zewxAqCj65WVbcF7UHLooFm7fezkgc=; b=h USYiIKUdlN02EU5Za1Og1Z1TiBLiuG4pPGH/rG/vhhi9S25VPrk52IUekG/iMf/E K1XrpYEL3nbxP2joZ8D91ASP9rjs1oSfvJGmeukuxukKsZXy1ow4PpxYby0uWm9C tcfvcamMe2JfAcDfsdfEF+DcQHER7/lysPrmT7oUs4MPNJy/4O6ixYoOF9cvOOHJ PIbX3DpCV6qLDr9IjTGT/j6qh04XDXRjczSV+BPCHudKkjOVQSmMlsHXgjjwR7Uj KTup1iARMaAB+tOZlOLapDRcgmTPcd65cXMzxbOvulE44dTbYU3w8Om8OXTORV5U PVQOZIrm72QNeEOF+2ytg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudehledgudegjecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepkfffgggfuffvvehfhfgjtgfgse htjeertddtfeejnecuhfhrohhmpeetughrihgrnhcumfhlrghvvghruceorggurhhirghn rdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomheqnecuggftrfgrthhtvghrnhepjeegtd fhuefhtefgffdvheduleetgeejudevffekteegjeeiheeuudellefgffffnecuvehluhhs thgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprggurhhirghnrdhklh grvhgvrhesrghklhgrvhgvrhdrtghomh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 12 Feb 2023 16:15:06 -0500 (EST) Message-ID: <5dbb0065-e0ac-a74b-889f-d8b0669f36b0@aklaver.com> Date: Sun, 12 Feb 2023 13:15:05 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.2 Subject: Re: pg_dump problem with postgres user To: ertan.kucukoglu@1nar.com.tr, david.g.johnston@gmail.com Cc: pgsql-general@lists.postgresql.org References: <001601d93f26$75663540$60329fc0$@1nar.com.tr> Content-Language: en-US From: Adrian Klaver In-Reply-To: <001601d93f26$75663540$60329fc0$@1nar.com.tr> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2/12/23 13:10, ertan.kucukoglu@1nar.com.tr wrote: > 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. Who is they? > Is it possible to put everything back to normal? If it was some outside entity that you don't know that changed the permissions then you can't trust the instance any more. > Can I use single user mode to change passwords and permissions? > > Thanks & Regards, > Ertan > > > -- Adrian Klaver adrian.klaver@aklaver.com