Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id E00BE1337B9D for ; Tue, 12 Oct 2010 17:08:24 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 26152-05 for ; Tue, 12 Oct 2010 20:08:16 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from gw.wicourts.gov (gwmta.wicourts.gov [165.219.244.99]) by mail.postgresql.org (Postfix) with ESMTP id 861511337B4B for ; Tue, 12 Oct 2010 17:08:16 -0300 (ADT) Received: from Courts-MTA by gw.wicourts.gov with Novell_GroupWise; Tue, 12 Oct 2010 15:08:16 -0500 Message-Id: <4CB479DB02000025000368A9@gw.wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 8.0.1 Date: Tue, 12 Oct 2010 15:08:11 -0500 From: "Kevin Grittner" To: "George Clark" , Subject: Re: default console user authentication? References: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-4.21 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201010/98 X-Sequence-Number: 35839 George Clark wrote: > I'm trying to do a pg_dump to backup a database that is part of > our phone system. The original installers (phone people) seem to > know nothing about the superuser account, or the db admin account, > and the pg_dump needs a password authentication. > > The pg_dump command is asking for the password for user > "Administrator." I'm logged into the server (a Windows Server) as > the Admin user, but it is NOT THAT password it wants, because that > one fails. I am using the command: > > pg_dump -p 6432 eware -f D:\Util\pgdump.log > > If they did not configure a default password at install, how can I > set up a superuser acct and password so I can do some admin work > with this pg database? Right now I have no console level access > to this thing. You might want to temporarily modify pg_hba.conf or pgpass to get through this, and then review how you want to handle security long term (which *might* involve making your emergency fix permanent). http://www.postgresql.org/docs/current/interactive/auth-pg-hba-conf.html http://www.postgresql.org/docs/current/interactive/libpq-pgpass.html -Kevin