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 1pDjqu-0002Ay-Ht for pgsql-general@arkaria.postgresql.org; Fri, 06 Jan 2023 10:21:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pDjqt-0001nr-Eq for pgsql-general@arkaria.postgresql.org; Fri, 06 Jan 2023 10:21:31 +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 1pDjqt-0001nh-3B for pgsql-general@lists.postgresql.org; Fri, 06 Jan 2023 10:21:31 +0000 Received: from mail-oo1-xc2e.google.com ([2607:f8b0:4864:20::c2e]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pDjqq-0007rn-SW for pgsql-general@lists.postgresql.org; Fri, 06 Jan 2023 10:21:30 +0000 Received: by mail-oo1-xc2e.google.com with SMTP id c190-20020a4a4fc7000000b004a3addd10b5so381416oob.1 for ; Fri, 06 Jan 2023 02:21:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=ZOo4XS0ziOV5Hk3E/68puZm5TAEBd3/6d/pS/roRa9I=; b=NvGJSXg5ai0U+inpfEqWsL5SW2H/t4idC0+GZbQvhrn3EIvH0evdcL2sDHrJTwIxu6 WtUDhQrOWHn7wrJuQxx8i9ynQ93xhbOpx+Dyw2tixbZat8DCG7FT1Mqq3OqYKCNeZ8wT 77ODwa0r02RL0eP5mWeQBMI5NJ7AYSPJ6R296+54OrhiL7nBvI/9bNx3afEE5F73FcGM mNduwVvPjgciT0HEv7rrII5B/I5X763OHdvJgcFQwJfleeTj2G4kVHiU5xSHS4P1Y/9J xpQVaJBdQ3PEoSAgPvAl9o9c0aYByuU0GGwMBxLTABzVfqQaootOG6IlVDdo7Su1hjBY V/Dg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=ZOo4XS0ziOV5Hk3E/68puZm5TAEBd3/6d/pS/roRa9I=; b=cH0gMGsaQ6dmGCaLijhKO812xyv6Z1a5jbvcilDx63aHwttZnp0fv/pgjToPtfrIE7 JRThkZ2Z+L03I2HbF+1LyAq5R5c9UPa97Lgdje61KssA22RtyFuABJU4/+Y74gzEl5Is 4EYCyOSFW8Fl9DeUTpuN7T8j/avKbBRbDX+NFVz4jeU4dnc7UerT09219zaQ1AtoRPtE i8KgjwMPy9TklTQRzKwdmXhdjDAhJf4K4B0woT/hU65SLU0Tq/dbHSLq5epgpif6znFa RsWUr3e9ytcZ3bs+Vltme07npqr5R6X8PG3VBogDQlA6YsO4frb0b2TOXsE/gSIiQsbu DFrg== X-Gm-Message-State: AFqh2koXsGexucMwJ8lqzVL+jd9FgbLSs7kYBfIGD0poTYE6XaL0Po8L ZK4xzCmw4CHI+NHvQ8T8vy98h7KhAAo= X-Google-Smtp-Source: AMrXdXtTtc8HSkCECtaWQ4XiCZkDu2lXeoa9WsfLy/KbDX46hO4mPdIgXRY6QAzzrA+atVGHn0d9sw== X-Received: by 2002:a05:6820:1391:b0:4aa:db53:e686 with SMTP id i17-20020a056820139100b004aadb53e686mr26983799oow.2.1673000487857; Fri, 06 Jan 2023 02:21:27 -0800 (PST) Received: from [192.168.1.66] (108-250-206-84.lightspeed.nworla.sbcglobal.net. [108.250.206.84]) by smtp.googlemail.com with ESMTPSA id h4-20020a4aa284000000b004db65419011sm258064ool.34.2023.01.06.02.21.27 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 06 Jan 2023 02:21:27 -0800 (PST) Message-ID: Date: Fri, 6 Jan 2023 04:21:26 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2 Subject: Re: best practice to patch a postgresql version? Content-Language: en-US To: pgsql-general@lists.postgresql.org References: <0a9d2078-1900-1e0c-be96-f4d5bdc6df22@gmail.com> <802bc09b7fa07f9fd1d7d8907a4b988f42af8d95.camel@cybertec.at> From: Ron In-Reply-To: <802bc09b7fa07f9fd1d7d8907a4b988f42af8d95.camel@cybertec.at> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 1/5/23 23:43, Laurenz Albe wrote: > 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 for 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 backpatches. I have > seen it happen once or twice in the 15+ years I have been dealing with PostgreSQL. > In that case, a new minor release will come out soon afterwards. It's absolutely standard practice "in the enterprise" to install the latest patch on the UAT (and possibly Dev and Staging) servers before rolling out to production. Have I aver seen a problem in Postgresql?  No.  But I've seen problems with other RDBMSs.  If a problem did happen, and caused for example, an important report to suddenly take 3 hours instead of 3 minutes, the client will scream; there might even be SLA penalties. Thus, we're cautious with "critical production databases". -- Born in Arizona, moved to Babylonia.