Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1etvOy-0003Kw-01 for pgsql-admin@arkaria.postgresql.org; Thu, 08 Mar 2018 13:16:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1etvOw-0000ZW-T6 for pgsql-admin@arkaria.postgresql.org; Thu, 08 Mar 2018 13:16:06 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1etvOw-0000ZD-Le for pgsql-admin@lists.postgresql.org; Thu, 08 Mar 2018 13:16:06 +0000 Received: from mx1.mailbox.org ([80.241.60.212]) by magus.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1etvOp-0006TX-Ly for pgsql-admin@postgresql.org; Thu, 08 Mar 2018 13:16:06 +0000 Received: from smtp2.mailbox.org (smtp2.mailbox.org [80.241.60.241]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.mailbox.org (Postfix) with ESMTPS id CE0F4429F5; Thu, 8 Mar 2018 14:15:57 +0100 (CET) X-Virus-Scanned: amavisd-new at heinlein-support.de Received: from smtp2.mailbox.org ([80.241.60.241]) by spamfilter02.heinlein-hosting.de (spamfilter02.heinlein-hosting.de [80.241.56.116]) (amavisd-new, port 10030) with ESMTP id d3p1ltO-a8gZ; Thu, 8 Mar 2018 14:15:56 +0100 (CET) Message-ID: <1520514955.2564.24.camel@cybertec.at> Subject: Re: Resetting database password From: Laurenz Albe To: Munyutu Waigi , pgsql-admin@postgresql.org Cc: Nduku Kitenge , "julius.osanjo" Date: Thu, 08 Mar 2018 14:15:55 +0100 In-Reply-To: References: Organization: Cybertec Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Munyutu Waigi wrote: > We desperately need assistance to regain access to our DB, TSAOMS Droplet. > Our developer (Fred Omala) has gone AWOL and our clients cannot access our solution. If local connections are allowed "trust" or "peer" authentication in pg_hba.conf, log into the database server as user "postgres" and start "psql". Then you can use ALTER ROLE to change database passwords. If all fails, you'll have to stop the database server and start it in single user mode (as operating system user "postgres"): postgres --single -D /your/database/directory postgres Then you are connected with superuser permissions and can change passwords. If all that is too complicated for you, contact a support company. Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com