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 1nQKEJ-0006eL-Oy for pgsql-performance@arkaria.postgresql.org; Sat, 05 Mar 2022 02:33:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nQKEH-0000us-2i for pgsql-performance@arkaria.postgresql.org; Sat, 05 Mar 2022 02:33:09 +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 1nQKEG-0000uh-P2 for pgsql-performance@lists.postgresql.org; Sat, 05 Mar 2022 02:33:08 +0000 Received: from mail-qt1-x835.google.com ([2607:f8b0:4864:20::835]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nQKED-0006zQ-It for pgsql-performance@lists.postgresql.org; Sat, 05 Mar 2022 02:33:08 +0000 Received: by mail-qt1-x835.google.com with SMTP id f18so9009711qtb.3 for ; Fri, 04 Mar 2022 18:33:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:date:mime-version:user-agent:to:content-language:from :subject; bh=57Ms1CmKlXybi0DGSHyY6wbEi9NPnUvPBDV3rcn+p7M=; b=Cf1cBQtgbqV6GGWsbfd0LeXKKDT2kAhdAQhNrZM1hUVE80I6l4d9j5WVnm4516Ltgh oO1EKMdQ1t29/bTAm889N6jCzrA8MbWUeWtE3cTObynKwDibSqOn7AwiCTo/scXEzFPc WncAUvOaAOA8VIB+szZIDlzXaVU+GTgGaL4o9Sv5bJdFRwz6FNsductpwPa+CU2vXlr0 GjtgJcU1v6FWqKaLXuKHtxZZhq2FMSLZKURvz046iyqurrQeWyOjLhLCTijnlkpW3+u5 ZIMEnDPABWZkKWhyiL/vr87oWaxp8BfUSvlARj4E/lAesYbZG9v9Kc4juNAsj0hZ+GAa gYkg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:to :content-language:from:subject; bh=57Ms1CmKlXybi0DGSHyY6wbEi9NPnUvPBDV3rcn+p7M=; b=6fZHwfW+iljQ5vMVoMGSuHqMv3FRuMhemhurL+l3AJ5yVM+C+zRnqD3ErcEZrxGwYI Kmmh2F3EhADbtt86hg19ZyliogAOuRCEIVRfPtZEru62mmkhbHUiGBaua5tguZ4ds7ks +77sIwrtMsD4iHlhrLgLtu8bn3+rGCyIlaB2dHIIS0gU3OvnYhZjbl3oziiRUKvGldDQ JD60/dSGjau15I7jYcFW+n0UkerbeuayN5y4ZMQJcNMrN1tpR7zqFHoI7cvbsyICR/kc c+JcVGRFdptPNEBlwSdcNdhk1ytI1oDEJ+U8f/ctLkp6RoPEgjxBMe7r5LQMSQnlNcvO 0LOA== X-Gm-Message-State: AOAM532qQSWbAKA4M+DPn98OrJ46mmsJX3ffSqYCHlbDEwJtgm5gew0Y QQ2jNcBnjTp/wNDIj4W9fo07d4eDWxs= X-Google-Smtp-Source: ABdhPJxomiAHxJW2pt/wcB6CBBMUzmLrqNSKasP/PI3XSohaB8afFP6oWxpn4FoCmnSU5y7WKNXK/A== X-Received: by 2002:a05:622a:5c8:b0:2df:f3d4:e214 with SMTP id d8-20020a05622a05c800b002dff3d4e214mr1468734qtb.183.1646447582918; Fri, 04 Mar 2022 18:33:02 -0800 (PST) Received: from [192.168.2.100] (pool-72-79-19-93.nwrknj.east.verizon.net. [72.79.19.93]) by smtp.gmail.com with ESMTPSA id i3-20020a05620a074300b006630cbe7ec0sm3487589qki.90.2022.03.04.18.33.02 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 04 Mar 2022 18:33:02 -0800 (PST) Content-Type: multipart/alternative; boundary="------------j5kdn3hkdI7vcHHnshdd6InI" Message-ID: Date: Fri, 4 Mar 2022 21:33:01 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 To: Pgsql Performance Content-Language: en-US From: Mladen Gogala Subject: XA transactions much slower on 14.2 than on 13.5 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------j5kdn3hkdI7vcHHnshdd6InI Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit My boss asked me to upgrade one of the developmentĀ  databases from 13.5 --> 14.2. One thing that we've noticed right away is that XA transactions (2-phase commit) are much slower on 14.2 than on 13.5. Were there any significant changes to the XA protocol in the version 14? Did anybody else encountered this problem? When I say "XA transactions are much slower", I mean that commit and/or rollback take much longer. The SQL execution takes the same and the plans are identical to the 13.5 version. The application code is the same, using IBM WebSphere 9.0.4. Regards -- Mladen Gogala Database Consultant Tel: (347) 321-1217 https://dbwhisperer.wordpress.com --------------j5kdn3hkdI7vcHHnshdd6InI Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

My boss asked me to upgrade one of the developmentĀ  databases from 13.5 --> 14.2. One thing that we've noticed right away is that XA transactions (2-phase commit) are much slower on 14.2 than on 13.5. Were there any significant changes to the XA protocol in the version 14? Did anybody else encountered this problem?

When I say "XA transactions are much slower", I mean that commit and/or rollback take much longer. The SQL execution takes the same and the plans are identical to the 13.5 version. The application code is the same, using IBM WebSphere 9.0.4.

Regards
-- 
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
https://dbwhisperer.wordpress.com
--------------j5kdn3hkdI7vcHHnshdd6InI--