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 1pDfVn-0004lb-In for pgsql-general@arkaria.postgresql.org; Fri, 06 Jan 2023 05:43:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pDfVm-0001wL-BO for pgsql-general@arkaria.postgresql.org; Fri, 06 Jan 2023 05:43:26 +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 1pDfVm-0001wB-0f for pgsql-general@lists.postgresql.org; Fri, 06 Jan 2023 05:43:26 +0000 Received: from mail-ed1-x531.google.com ([2a00:1450:4864:20::531]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pDfVj-0000I5-Ue for pgsql-general@lists.postgresql.org; Fri, 06 Jan 2023 05:43:25 +0000 Received: by mail-ed1-x531.google.com with SMTP id z11so1004231ede.1 for ; Thu, 05 Jan 2023 21:43:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20210112.gappssmtp.com; s=20210112; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:from:to:cc:subject:date :message-id:reply-to; bh=uM1GEdOP8Q7QYAWpdPXClxZ5y547otH51kunk5nsmbo=; b=HajFmqJc8iyiLRKZGbyEUT8qxM/HU2rs8TsKieB46uaUaNkUQUc3W+mF2C9PnQIxLY MIecDtty5s7mGhyuq0ELC/XRxE5jSkQlirq0T7r5JPy2D340XFX8ylDNvQb5+yhFmJH2 EVR14TPg4EOEI/VmsqVLSj4JLar/HgB23Xn6Ocis4xi4UH9Kmxd5CQtoK1176W8JvKdk 0CGdmel7bdZQryq6NIT4FV3PXqXoDVakYOB/uDigR5BhVYa3t4GP+Sx472jTEkgo9PXk Q67/2x7QgtIu9z9qxepRblhKWefmfw9LQIZWFJRKWNTDCOrfdHhVMHu53I4y/+uNWquz 3/Gg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=uM1GEdOP8Q7QYAWpdPXClxZ5y547otH51kunk5nsmbo=; b=3qkurprjY6KSwF7K8rDgkVwr8B5wBkc03MMM9jiFtjzHYA6WtgBhbDvhWJWonHu2Oz NtNiI5IWU9hHXHfpWgSv/TPR8n0SmZrX8vGvVkm184vlSl93QPK5Kr7zjyzi17pSG23s x090Z2KU4Hqy4oDFiKiwpvmbYTAo8aWkbBg/x4oXVh62DxrOlF4yNUDSiYlaKGrg0qbw IX8yycOoYSlIszVXySbAbCpO3lDbxDNSCzb0MpdgkDPxAjTChCku27XuJt7Kq5yIMCta Y8Nm6wEF7EbTyKBp+OsDVfn0QIhwFJEpb4b5ElsuX3lZBa+U8ZHGTaKOrNazP8IRAqjg +Abw== X-Gm-Message-State: AFqh2krpL2hhwpreh4ZWmXmMPqe9dNoxVCF6BY2Zqzfi+qsmAqG5FR0z SZu6YLCV0VxJDPImaF1Ab44CnhV7QLBfK31e X-Google-Smtp-Source: AMrXdXvi7UeMx8uXLtuxybWYlef533SST5eFC2Ja5HqEVg4obcYrq6C5vIO4pydVlGbyS+TZziFcJw== X-Received: by 2002:a05:6402:551b:b0:46a:732e:fd29 with SMTP id fi27-20020a056402551b00b0046a732efd29mr48917071edb.42.1672983803003; Thu, 05 Jan 2023 21:43:23 -0800 (PST) Received: from localhost.localdomain (62-46-248-108.adsl.highway.telekom.at. [62.46.248.108]) by smtp.gmail.com with ESMTPSA id b12-20020a05640202cc00b0046ee136fa3bsm146646edx.69.2023.01.05.21.43.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 05 Jan 2023 21:43:22 -0800 (PST) Message-ID: <802bc09b7fa07f9fd1d7d8907a4b988f42af8d95.camel@cybertec.at> Subject: Re: best practice to patch a postgresql version? From: Laurenz Albe To: Ron , pgsql-general@lists.postgresql.org Date: Fri, 06 Jan 2023 06:43:22 +0100 In-Reply-To: <0a9d2078-1900-1e0c-be96-f4d5bdc6df22@gmail.com> References: <0a9d2078-1900-1e0c-be96-f4d5bdc6df22@gmail.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.46.2 (3.46.2-1.fc37) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, 2022-12-27 at 00:48 -0600, Ron wrote: > If it really is a critical production database, you will have a CAT/UAT (= customer/user acceptance testing) > server on which you rigorously run regression tests on a point release fo= r a month before updating the production server. > > Otherwise, it's a hope-and-pray database. No, that is wrong. You should not test your application when you install a minor update. The = reason is that few people are willing to test the application thoroughly every few months,= and the outcome is that minor releases are *not* applied regularly, as they should be. You are supposed to trust PostgreSQL development that they don't introduce = new bugs. Sure, this can happen, even though all possible care is taken with backpatc= hes. I have seen it happen once or twice in the 15+ years I have been dealing with Post= greSQL. In that case, a new minor release will come out soon afterwards. Concerning the risks that you have to consider here (running into a known b= ug that is fixed in the latest minor release versus running into a bug introduced by t= he latest minor release), the PostgreSQL page makes this statement: > For minor releases, the community considers not upgrading to be riskier t= han upgrading. Of course you will update your test databases first, to make sure that your= update procedure is working well. Yours, Laurenz Albe