Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qjmBM-00C3Vs-Ta for pgsql-general@arkaria.postgresql.org; Fri, 22 Sep 2023 19:51:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qjmBL-0065H9-3x for pgsql-general@arkaria.postgresql.org; Fri, 22 Sep 2023 19:51:19 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qjmBK-0065Gn-9O for pgsql-general@lists.postgresql.org; Fri, 22 Sep 2023 19:51:18 +0000 Received: from bosmailout02.eigbox.net ([66.96.184.2]) by magus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qjmBF-006z8Y-M1 for pgsql-general@lists.postgresql.org; Fri, 22 Sep 2023 19:51:17 +0000 Received: from bosmailscan10.eigbox.net ([10.20.15.10]) by bosmailout02.eigbox.net with esmtp (Exim) id 1qjmBD-0003La-2b for pgsql-general@lists.postgresql.org; Fri, 22 Sep 2023 15:51:11 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=interthink.com; s=dkim; h=Sender:Content-Type:MIME-Version:Message-ID:Date: Subject:To:From:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=QW0FqanE5U9doScSW2NtCbW1CNTuyhcvtC57xH+/G14=; b=DRg7/pL6WN7jM1/6kxmNKcI7F6 IhrY7pDiD8evf6YvRpyrc08ufUSiJdq1NbrcYpaNbOyTPisNymPEJVWk3kQVTyeX6xCzfikDZ28aF U/ZcvPYX6mmigv9TOR5V6ZP7GKh/GphN6nkMCUhe1Q84w9nHrhvQTF9KxS9qxk8U+Dr5iOtGnlsOZ Bdsuedu+C/xKHQDLnchylO2yXzms4f/KpyFCXgN6ni0wFss/6d/nxDR0Jicnir05nzoaZTQRZjDjb XZ3B4AiNNBx0ML40H3zyo3JRE0fHcI+Gn1lAj8mp/tzgi9sqciBiRYkc1XR65+Fi6/07vUm3+MioH eouDinDQ==; Received: from [10.115.3.32] (helo=bosimpout12) by bosmailscan10.eigbox.net with esmtp (Exim) id 1qjmBC-00089v-21 for pgsql-general@lists.postgresql.org; Fri, 22 Sep 2023 15:51:10 -0400 Received: from bosauthsmtp10.yourhostingaccount.com ([10.20.18.10]) by bosimpout12 with id p7r62A0080D2CUy017r9c8; Fri, 22 Sep 2023 15:51:10 -0400 X-Authority-Analysis: v=2.3 cv=d4VuNSrE c=1 sm=1 tr=0 a=Kpo39fPXdbgqDwiI3/AEUA==:117 a=gWXr5l5jm78BjrOez5gLrA==:17 a=zNV7Rl7Rt7sA:10 a=DAwyPP_o2Byb1YXLmDAA:9 a=pAJwVq4hvFDxY_QHh0IA:9 a=CjuIK1q_8ugA:10 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=W4A2ksPxYcdxH3VYkvoA:9 a=gKO2Hq4RSVkA:10 a=UiCQ7L4-1S4A:10 a=hTZeC7Yk6K0A:10 a=frz4AuCg-hUA:10 Received: from d149-67-38-110.try.wideopenwest.com ([67.149.110.38]:64211 helo=DESKTOPEG43I6B) by bosauthsmtp10.eigbox.net with esmtpsa (TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim) id 1qjmB8-0007mi-DI for pgsql-general@lists.postgresql.org; Fri, 22 Sep 2023 15:51:06 -0400 From: To: Subject: StackBuilder unexpected restart Date: Fri, 22 Sep 2023 15:51:04 -0400 Message-ID: <003f01d9ed8e$206aa820$613ff860$@interthink.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0040_01D9ED6C.9959CB70" X-Mailer: Microsoft Outlook 16.0 Thread-Index: Adntih+f1W7RmrKbR+C5/QofirAOFw== Content-Language: en-us X-EN-UserInfo: 49a7df039afd4e0ebb942ef52d8fd6fa:931c98230c6409dcc37fa7e93b490c27 X-EN-AuthUser: russcampbell@interthink.com Sender: X-EN-OrigIP: 67.149.110.38 X-EN-OrigHost: d149-67-38-110.try.wideopenwest.com List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multipart message in MIME format. ------=_NextPart_000_0040_01D9ED6C.9959CB70 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I downloaded and installed Postgres 15.4 and then let StackBuilder run. All I installed was pgAgent and the four drivers. The software notified me that I should choose "Restart Later" or "No" if I was asked about restarting. Instead of getting that type of question along the way, I got no such questions. Fine. Figured the software needing to be installed didn't need a reboot (why would drivers need that, after all?). But, without any warning, the installation rebooted my server. Just all of a sudden - bam!. No warning. This was on a production server. Now, I did this because 1) I was led to believe that there would be no forced restart and 2) the transaction rate on this server is low and, frankly, a reboot like this is unlikely to cause any problems for this server. However, there's no excuse for unannounced reboots. It should always involve user permission except in a silent install. Why is this software allowed to do this?! In advance, let me say I hope I don't get any "you shouldn't have done this on a server during business hours." Well, 1) I've already explained why, and 2) developers should never use that to shirk responsibility. Reboots should always be authorized by the user. If a mandatory reboot is required at the exact moment of installation for some reason, that should be disclosed very clearly at the outset. ------=_NextPart_000_0040_01D9ED6C.9959CB70 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I downloaded and installed = Postgres 15.4 and then let StackBuilder run. All I installed was pgAgent = and the four drivers. The software notified me that I should choose = “Restart Later” or “No” if I was asked about = restarting. Instead of getting that type of question along the way, I = got no such questions. Fine. Figured the software needing to be = installed didn’t need a reboot (why would drivers need that, after = all?). But, without any warning, the installation rebooted my server. = Just all of a sudden – bam!. No warning. This was on a production = server. Now, I did this because 1) I was led to believe that there would = be no forced restart and 2) the transaction rate on this server is low = and, frankly, a reboot like this is unlikely to cause any problems for = this server. However, there’s no excuse for unannounced reboots. = It should always involve user permission except in a silent = install.

 

Why is this software allowed to do this?! In advance, = let me say I hope I don’t get any “you shouldn’t have = done this on a server during business hours.” Well, 1) I’ve = already explained why, and 2) developers should never use that to shirk = responsibility. Reboots should always be authorized by the user. If a = mandatory reboot is required at the exact moment of installation for = some reason, that should be disclosed very clearly at the = outset.

------=_NextPart_000_0040_01D9ED6C.9959CB70--