From amgostick@navdata.ca Tue Jul 7 07:03:08 2026 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 1kDA0R-0003QE-Tr for pgsql-novice@arkaria.postgresql.org; Tue, 01 Sep 2020 17:23:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kDA0Q-0002r1-Rx for pgsql-novice@arkaria.postgresql.org; Tue, 01 Sep 2020 17:23:38 +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 1kDA0Q-0002qt-LV for pgsql-novice@lists.postgresql.org; Tue, 01 Sep 2020 17:23:38 +0000 Received: from mailout.easymail.ca ([64.68.200.34]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kDA0O-0007xP-Gj for pgsql-novice@lists.postgresql.org; Tue, 01 Sep 2020 17:23:38 +0000 Received: from localhost (localhost [127.0.0.1]) by mailout.easymail.ca (Postfix) with ESMTP id 3BCF5A1BF8 for ; Tue, 1 Sep 2020 17:23:34 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at emo05-pco.easydns.vpn Received: from mailout.easymail.ca ([127.0.0.1]) by localhost (emo05-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8633NCjw4qzR for ; Tue, 1 Sep 2020 17:23:34 +0000 (UTC) Received: from webmail.easymail.ca (unknown [172.17.13.103]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailout.easymail.ca (Postfix) with ESMTPSA id 00B2EA1BF7 for ; Tue, 1 Sep 2020 17:23:33 +0000 (UTC) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_f2afd2311e80909a293c7121b00d4937" Date: Tue, 01 Sep 2020 13:23:33 -0400 From: Albert Gostick To: pgsql-novice@lists.postgresql.org Subject: Implications of resetting Postgres service in Windows Organization: Navdata IT Systems Message-ID: <1a9e822d9817f26ad376c8cd39f85c88@navdata.ca> X-Sender: amgostick@navdata.ca User-Agent: Roundcube Webmail/1.3.3 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --=_f2afd2311e80909a293c7121b00d4937 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII We have Postgres 9.4 installed on Win2012. It was installed by an outside contractor years ago. I was asked to review and change all the passwords used in Postgres (along with another product) and noticed that on this server, the postgres service "postgresql-x64-9.4" runs under the "Network Service" account and it has a password associated with it. I sort of think I can guess the password used by the developer, but I cannot be sure. If I change this password, what are the implications: a) nothing - the password is only used to secure the service running or b) the password also needs to be changed somehow within the database (using pgAdmin I assume - although I have not found a screen there to change the superuser password). Any suggestions would be appreciated! I just want to update the passwords as per higher management but not knock out the server! Thanks. --=_f2afd2311e80909a293c7121b00d4937 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8

We have Postgres 9.4 installed on Win2012.  It was installed by an = outside contractor years ago.

I was asked to review and change all the passwords used in Postgres (alo= ng with another product) and noticed that on this server, the postgres serv= ice "postgresql-x64-9.4" runs under the "Network Service" account and it ha= s a password associated with it.

I sort of think I can guess the password used by the developer, but I ca= nnot be sure.

If I change this password, what are the implications:

a) nothing - the password is only used to secure the service running

or

b) the password also needs to be changed somehow within the database (us= ing pgAdmin I assume - although I have not found a screen there to change t= he superuser password).

Any suggestions would be appreciated!  I just want to update the pa= sswords as per higher management but not knock out the server!

Thanks.

--=_f2afd2311e80909a293c7121b00d4937-- From tgl@sss.pgh.pa.us Tue Jul 7 07:03:08 2026 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 1kDAW6-0004r7-07 for pgsql-novice@arkaria.postgresql.org; Tue, 01 Sep 2020 17:56:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kDAW4-0001TM-62 for pgsql-novice@arkaria.postgresql.org; Tue, 01 Sep 2020 17:56:20 +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 1kDAW3-0001T9-W9 for pgsql-novice@lists.postgresql.org; Tue, 01 Sep 2020 17:56:19 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kDAW1-0002Dr-Tk for pgsql-novice@lists.postgresql.org; Tue, 01 Sep 2020 17:56:18 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 081HuGoh141595; Tue, 1 Sep 2020 13:56:16 -0400 From: Tom Lane To: Albert Gostick cc: pgsql-novice@lists.postgresql.org Subject: Re: Implications of resetting Postgres service in Windows In-reply-to: <1a9e822d9817f26ad376c8cd39f85c88@navdata.ca> References: <1a9e822d9817f26ad376c8cd39f85c88@navdata.ca> Comments: In-reply-to Albert Gostick message dated "Tue, 01 Sep 2020 13:23:33 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <141593.1598982976.1@sss.pgh.pa.us> Date: Tue, 01 Sep 2020 13:56:16 -0400 Message-ID: <141594.1598982976@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Albert Gostick writes: > We have Postgres 9.4 installed on Win2012. It was installed by an > outside contractor years ago. > I was asked to review and change all the passwords used in Postgres > (along with another product) and noticed that on this server, the > postgres service "postgresql-x64-9.4" runs under the "Network Service" > account and it has a password associated with it. > I sort of think I can guess the password used by the developer, but I > cannot be sure. > If I change this password, what are the implications: > a) nothing - the password is only used to secure the service running > or > b) the password also needs to be changed somehow within the database > (using pgAdmin I assume - although I have not found a screen there to > change the superuser password). (a) is correct; whatever password the operating system account may have is irrelevant to, indeed not known to, the Postgres server. You will need to be sure that the server can still be started successfully, of course. (It is of course possible that the previous admin used the same password inside the database as for the OS account, but that would be a chance coincidence from our standpoint.) regards, tom lane