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 1mHZJ2-0007ZV-GB for pgsql-performance@arkaria.postgresql.org; Sat, 21 Aug 2021 22:17:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mHZJ0-0007RO-IC for pgsql-performance@arkaria.postgresql.org; Sat, 21 Aug 2021 22:17:34 +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 1mHZJ0-0007MT-9b for pgsql-performance@lists.postgresql.org; Sat, 21 Aug 2021 22:17:34 +0000 Received: from mail-io1-xd2a.google.com ([2607:f8b0:4864:20::d2a]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mHZIx-0004Wy-JQ for pgsql-performance@postgresql.org; Sat, 21 Aug 2021 22:17:33 +0000 Received: by mail-io1-xd2a.google.com with SMTP id y18so1301825ioc.1 for ; Sat, 21 Aug 2021 15:17:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=V7GR50sva5Zsltiad9v8FsM05k86V5yxSrN9s8y6uSY=; b=v3fiC5OpmQIjmKT+IC3WyckviHaq4xHVKSFbD76TnA2QsgF9ZXcCTtilYbQW0TbN0G FvpluecuPViST56gGS9nbZQXex38wWW1h2nVznd5J5pU+RBEP0PlrQ01LGKQ5Fg1GZzo e/U0fex72os5n8eorZqK9OY2UwYoTvsH+gcDuNyJ+dnb1sAnVQzaG8l+2zDf2BreBqpT LP9TwRoOYGEo0jVdkzlpFE1RtxHFmUFqE5pc4IaVSS3zATcMwK6OkpDAY3lIck0WGPgF M7XVJiA7SDcpjQovMmCGZQtt96SP4Dnhq5jUqneK8xIjYD/HJMIoqqbdb6KrnIadzr9e q7xA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=V7GR50sva5Zsltiad9v8FsM05k86V5yxSrN9s8y6uSY=; b=LwTST1nCJhI5OBQO8VGcr0pOvjYAyQkzUzdhagStmDTIqB3Gz2sc6N2YyySlqg5Ckx uekI4MVjI+Uklb6rw8diyNU/cawtn4Plo4fGU3W7Cusk8NxBmyU1eua9mZ49OsBcJ8qy Rn2+Up+iZHEh3KKxur+h1orSeGiqcLxE+/7x3cxHJd2qR+T7nVur9mc3I19I/P65Qw13 BnHtkiUeCduTFptauN+0V8Fc9V2Gf0JtQUBGI8rwPclYc1RWRlENfuxO4/VCWROUzywn XVwLrvHXSxZeiQua6G2DjQ8arHMSTzM9veCR/xjP2WPtenU+HUkCSDLZUzgr4uRhsRyn aQow== X-Gm-Message-State: AOAM531HmHcLO8YuhkW8AUdrVJ2xPUu3msTrsDx0JkCxehSuSLqLaY0t j+PFiyRQIprhDXYhJZyKZhcVnw== X-Google-Smtp-Source: ABdhPJxWJmBIwYh8Jm5lE9ei0sH2mF+UmxetRZgryLRqXCF4x8U4G+QKZ2Km4Jf3sr4n82Dlv82a1Q== X-Received: by 2002:a05:6638:304a:: with SMTP id u10mr23956365jak.62.1629584250687; Sat, 21 Aug 2021 15:17:30 -0700 (PDT) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id e1sm5754525ils.76.2021.08.21.15.17.30 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 21 Aug 2021 15:17:30 -0700 (PDT) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 645D5800BDB; Sat, 21 Aug 2021 17:17:29 -0500 (CDT) Date: Sat, 21 Aug 2021 17:17:29 -0500 From: Justin Pryzby To: ldh@laurent-hasson.com Cc: Tom Lane , pgsql-performance@postgresql.org Subject: Re: Big Performance drop of Exceptions in UDFs between V11.2 and 13.4 Message-ID: <20210821221729.GY10479@telsasoft.com> References: <2092859.1629558281@sss.pgh.pa.us> <2136207.1629569846@sss.pgh.pa.us> <20210821191950.GW10479@telsasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Could you send SELECT * FROM pg_config() and try to find the CPU model ? I think it's possible the hypervisor is trapping and emulating unhandled CPU instructions. Actually, it would be interesting to see if the performance differs between 11.2 and 11.13. It's possible that EDB compiled 11.13 on a newer CPU (or a newer compiler) than 11.2 was compiled. If you test that, it should be on a separate VM, unless the existing data dir can be restored from backup. Once you've started a cluster with updated binaries, you should avoid downgrading the binaries.