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 1osaFG-0000eJ-7B for pgsql-admin@arkaria.postgresql.org; Wed, 09 Nov 2022 01:51:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1osaFE-0001oC-0t for pgsql-admin@arkaria.postgresql.org; Wed, 09 Nov 2022 01:51:12 +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 1osaFD-0001o3-Kd for pgsql-admin@lists.postgresql.org; Wed, 09 Nov 2022 01:51:11 +0000 Received: from mail-oa1-x2f.google.com ([2001:4860:4864:20::2f]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1osaF9-00073M-SV for pgsql-admin@lists.postgresql.org; Wed, 09 Nov 2022 01:51:11 +0000 Received: by mail-oa1-x2f.google.com with SMTP id 586e51a60fabf-13bef14ea06so18258675fac.3 for ; Tue, 08 Nov 2022 17:51:07 -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=5ot7gyPwXvJFDSZO/8uyhdhD1Yr0FsSpL2B3UWYCwIo=; b=B10YqgoMSQrAKJWMez6OL9sCeJyhBO05PbL99XZ9ZgxjXKMe3b+OiyDA7meA6QIOo4 fe70mUVxTiLXi3Sb+fkaD4cjwFI6+ZlDWPX4Ppk/0mLx21+ySHUwBukd6dV0zTobHEtR spCTCtgbDgUk5uVMNOJNm1ZsCia+pHubELF0X63SWtOqLwf0qDb2Z82aO3clCQ29NRys UfuTNNVjWktBI6L3zITHz11xF3g2VZcKB081If303kWDgJYBoX91pDX7D076y4Ig8XFQ KdVWdy9GKWip4LTeotB6La0+IoHKBU2MsKxERKW7Wnz6uDWjyaAymbexyrXq6Ianno1O lz7g== 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=5ot7gyPwXvJFDSZO/8uyhdhD1Yr0FsSpL2B3UWYCwIo=; b=HcbzEo3ScNecAnA0/07NODXycySg1Z4WqCiP5pbv3oiMJlsplE3mfT34qjIiEH3zpM wCEMomUO883GOnooZJtfXjOr6Thz56zcVpPoQlsV4+2iVFzOFes83cB5JX0rqiT1Jasz mtOI/9Errwjg1W5hECTx1Sn32aBd1ITvnexr5o1GcegcSff7oh4vY270Lv+vZpeuoFft RS70m34HVUkETHqciV+GkvES7pWCSDwZUgkPJSkwIuUTkiH4mYLATHZji5YZIJjWy76c gV4geVsP+yNDPJmXXK2g3eMgeykB1gsEbAyipqX7cbYzEQVefqyOqRbVnfEebm3enxC9 ts5w== X-Gm-Message-State: ACrzQf05OxIsR138Et2dT/2AUGp3YkZ8XUAj9CTr+mR2hopj3mAAe2nV Qt2lk77zY4//7AIQSyjpkv9j/KlPeoY= X-Google-Smtp-Source: AMsMyM4TG+0VXDJ1//QrVTVkVl3PYQv78XxfXhc+6kHx/7Tw/TCpV8Vn2q0L8GpUh61T/rweDuEkBw== X-Received: by 2002:a05:6870:911f:b0:13b:b62e:1595 with SMTP id o31-20020a056870911f00b0013bb62e1595mr44075697oae.32.1667958665288; Tue, 08 Nov 2022 17:51:05 -0800 (PST) Received: from [192.168.88.10] (ip68-11-68-85.no.no.cox.net. [68.11.68.85]) by smtp.googlemail.com with ESMTPSA id g11-20020a056870340b00b0011bde9f5745sm5418550oah.23.2022.11.08.17.51.04 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 08 Nov 2022 17:51:04 -0800 (PST) Message-ID: <6c56ead3-4464-d7bb-dc8c-366d7517a327@gmail.com> Date: Tue, 8 Nov 2022 19:51:04 -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: Slowness after 13.7 -> 14.4 Content-Language: en-US To: pgsql-admin@lists.postgresql.org References: From: Ron In-Reply-To: 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 11/8/22 18:06, Wells Oliver wrote: > Upgraded 13.7 to 14.4 on RDS by restoring from a snapshot and upgrading that. Off-topic, but did you rebuild all indices with text columns?  That might not be relevant in RDS (who knows exactly what's underneath the hood?) but it might be. > My configuration files and instance type are exactly the same. After > upgrading, I ran vacuumdb -Z  -j 8 and that did its thing. > The upgraded database is slower. I'm running EXPLAIN ANALYZE for various > queries and it's getting to the same plan, but it's taking longer to execute. > > I've always felt after major upgrades there's some element to "priming the > database" where it seems to be much faster a few days in after broader > usage. I realize it sounds absurd but I'll swear by this being my > experience. So I'm willing to think to some degree that queries will > execute faster the more people use the upgraded database. > > Just wondering if there is anything I might specifically look at that > would account for some of the slowness. https://dba.stackexchange.com/a/295145/63913 That answer is about loading the cache yourself, either the old school SELECT * FROM foo WHERE ... method, or using using the pg_prewarm extension. -- Angular momentum makes the world go 'round.