X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 1716854421; Fri, 4 Mar 2005 21:07:59 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 92761-02; Fri, 4 Mar 2005 21:07:57 +0000 (GMT) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by svr1.postgresql.org (Postfix) with ESMTP id 3DE4854F47; Fri, 4 Mar 2005 21:07:56 +0000 (GMT) Received: from dopey (h00095b88257d.ne.client2.attbi.com[65.96.132.27]) by comcast.net (rwcrmhc12) with SMTP id <2005030421075701400jjb3oe>; Fri, 4 Mar 2005 21:07:57 +0000 From: "Hagop H." To: , , , Subject: PostgreSQL installation problem on Windows XP Home Date: Fri, 4 Mar 2005 16:07:52 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0079_01C520D4.5214D620" X-Mailer: Microsoft Office Outlook, Build 11.0.6353 Thread-Index: AcUg/joRA//YE0iMSQKZAu1wXkCBYA== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Message-Id: <20050304210756.3DE4854F47@svr1.postgresql.org> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=3.55 tagged_above=0 required=5 tests=DNS_FROM_RFC_ABUSE, DNS_FROM_RFC_POST, HTML_50_60, HTML_MESSAGE, MSGID_FROM_MTA_ID X-Spam-Level: *** X-Archive-Number: 200503/59 X-Sequence-Number: 16557 This is a multi-part message in MIME format. ------=_NextPart_000_0079_01C520D4.5214D620 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I know that my problem is due to my carelessness and ignorance, but I didn't think that installing PostgreSQL would cause a state of affairs not easily reversed. Please excuse the length of the following narrative. When installing PostgreSQL 8.0.1 on my laptop running Windows XP Home (SP2), I let the installer create the postgres account and generate a password. I didn't write down the password. I figured that if the installer was going to generate a random password, it would store it in some configuration or log file and not ask me for it. I was wrong. (Perhaps a warning for idiots like me would be appropriate in the MSI installer file?) When I went to connect to the template1 database, PGAdmin III asked me for the postgres account password, which I was unable to provide. Normally this wouldn't be a problem. I figured I'd just start up Control Panel and change the postgres account password. Unfortunately, Windows XP Home doesn't provide any obvious tools to change a system account password. I only know how to change user account passwords. Control Panel's User Accounts tool is useless for this problem. I uninstalled PostgreSQL, thinking that reinstalling it might help. I tried removing the postgres account to no avail. My only indication that the postgres account still exists is the Windows Services administration utility. I know of no method to delete the account. Microsoft's Knowledge Base provided no help. Windows XP Professional contains a tool called Local Users and Groups (lusrmgr.msc) that allows the administrator to change any account's password. Windows XP Home cannot run that program. When I reinstall PostgreSQL, I am asked for the postgres account password. I know I could rename the postgres account name to postgres1 or something else, but I don't know if that will create any further issues for me. I could also upgrade the laptop's OS to XP Pro in order to change the postgres account password, but that feels like using a sledgehammer to cut diamonds. I certainly bear most of the blame. It would be too easy to bash Microsoft for this. I also wish that PostgreSQL's installer did not auto-generate passwords that cannot be changed. None of what I went through was necessary. If someone could tell me either how to delete the postgres account or change its password, I would appreciate the assistance. Regards, Hagop Hagopian ------=_NextPart_000_0079_01C520D4.5214D620 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I know that my problem is due to my carelessness and ignorance, but I didn’t think that installing PostgreSQL would = cause a state of affairs not easily reversed. Please excuse the length of the = following narrative.

 

When installing PostgreSQL 8.0.1 on my laptop running = Windows XP Home (SP2), I let the installer create the postgres account and = generate a password. I didn’t write down the password. I figured that if the installer = was going to generate a random password, it would store it in some = configuration or log file and not ask me for it. I was wrong. (Perhaps a warning for = idiots like me would be appropriate in the MSI installer file?) When I went to = connect to the template1 database, PGAdmin III asked me for the postgres account = password, which I was unable to provide.

 

Normally this wouldn’t be a problem. I figured = I’d just start up Control Panel and change the postgres account password. = Unfortunately, Windows XP Home doesn’t provide any obvious tools to change a = system account password. I only know how to change user account passwords. Control = Panel’s User Accounts tool is useless for this = problem.

 

I uninstalled PostgreSQL, thinking that reinstalling = it might help. I tried removing the postgres account to no avail. My only = indication that the postgres account still exists is the Windows Services = administration utility. I know of no method to delete the account. Microsoft’s = Knowledge Base provided no help. Windows XP Professional contains a tool called = Local Users and Groups (lusrmgr.msc) that allows the administrator to change = any account’s password. Windows XP Home cannot run that program. =

 

When I reinstall PostgreSQL, I am asked for the = postgres account password. I know I could rename the postgres account name to = postgres1 or something else, but I don’t know if that will create any = further issues for me. I could also upgrade the laptop’s OS to XP Pro in = order to change the postgres account password, but that feels like using a = sledgehammer to cut diamonds.

 

I certainly bear most of the blame. It would be too = easy to bash Microsoft for this. I also wish that PostgreSQL’s installer = did not auto-generate passwords that cannot be changed. None of what I went through was = necessary.

 

If someone could tell me either how to delete the = postgres account or change its password, I would appreciate the = assistance.

 

Regards,

 

Hagop Hagopian

------=_NextPart_000_0079_01C520D4.5214D620--