Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qzNrd-00Fvt5-3H for pgsql-performance@arkaria.postgresql.org; Sat, 04 Nov 2023 21:07:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qzNrb-007MWV-Cx for pgsql-performance@arkaria.postgresql.org; Sat, 04 Nov 2023 21:07:27 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qzNra-007MWN-VY for pgsql-performance@lists.postgresql.org; Sat, 04 Nov 2023 21:07:27 +0000 Received: from mail-wm1-x32a.google.com ([2a00:1450:4864:20::32a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qzNrW-003yif-Jz for pgsql-performance@postgresql.org; Sat, 04 Nov 2023 21:07:25 +0000 Received: by mail-wm1-x32a.google.com with SMTP id 5b1f17b1804b1-40838915cecso24134805e9.2 for ; Sat, 04 Nov 2023 14:07:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20230601.gappssmtp.com; s=20230601; t=1699132040; x=1699736840; darn=postgresql.org; 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=hKQFNotBb5aGdCWe6onk9lSaK+u/+gripSgre/aa0FA=; b=P4HF3JhY2Mv7Rs4yoJXEk/a6RC1Jnqc7DHXe9uwEwSb8VxF2E0nxkg837KVYmnnnNx koP22YLRWkEMGNGiGK5xOGJUM5Ikl3sSE8wSqvBOVeGFpzjunDdiuaP+NN6/PDd4h3Mz q2dwAq0Ou7HV4OF7ZNDn6x+dMz11Dx3FD4QcoWy9qzsgCpcNCqdiX8CzRIYyxG2y9YlG gMka73+WCeXbDrCcPGN2vuk4hlJiRQNUqFJah4/Hdco3jxI+TBqDce4jZnXx4+tZqwSp COsXyAZjZte8++CE+3SI4VtamM8NfgOS8xhGtzENpny3p1AwRpOU+AFjH8MeSrM4ettV hszw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699132040; x=1699736840; 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=hKQFNotBb5aGdCWe6onk9lSaK+u/+gripSgre/aa0FA=; b=B2Ob7Mz4iyUxwcbaekEfVGFLPl4O51F6mpQN82j821BNMafA7pn3HhA5NiL2usxbdc r/B3h3EJ8twvyu7Gbc31xmQ6sfiuj2cuS/65GUE7/mqjGGLk0MXs1/behr7VXOlgTrVM +fhmE25pMyWmDhWt6yCSO0vJgf7Hhb9tC/mqUuEBzUM3Gg0EOrDl+T6PAC47UpelZz/O I9FufJvBm9O4gTjFGGlmTrlcQHmi97MbCZth7LBuFzISGJCOa3bXkLyAPVgB2Voyc2+W aDf/FhzYQ0rXb8+a2KPHkTaP0wQB0KtSiiQOlHcOC1+ZLK6zlEE08MLpw3Um3V7Fgq1k o43g== X-Gm-Message-State: AOJu0YyEpXZXM1uA2YgrZS3UvBYPUvvQHFleY2EQdL3K06a8y72maFHU c6G3t4QCt1YD8CbH0f0bYPi2uw== X-Google-Smtp-Source: AGHT+IEv2Hwx5RIElHx+SU63s23ONbLecMNKbYfvmQlgN8Al7dExCCRvbR85jTpj1TsrNf+MfljTMQ== X-Received: by 2002:a05:600c:1f88:b0:409:404e:5b9a with SMTP id je8-20020a05600c1f8800b00409404e5b9amr15214308wmb.33.1699132039916; Sat, 04 Nov 2023 14:07:19 -0700 (PDT) Received: from localhost.localdomain ([2001:871:260:349a:57ab:e7ee:d613:d164]) by smtp.gmail.com with ESMTPSA id h19-20020a05600c30d300b004063c9f68f2sm6784782wmn.26.2023.11.04.14.07.19 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 04 Nov 2023 14:07:19 -0700 (PDT) Message-ID: Subject: Re: Performance down with JDBC 42 From: Laurenz Albe To: "Abraham, Danny" , psql-performance Date: Sat, 04 Nov 2023 22:07:19 +0100 In-Reply-To: References: <5c1179bb-240b-4c1c-b4b3-2a24868e44bc@stiltsoft.com> <1570249.1697228785@sss.pgh.pa.us> <3153246.1697661350@sss.pgh.pa.us> <1157086.1698329377@sss.pgh.pa.us> <6c888a16-b206-4817-b5ca-9e09b904edde@stiltsoft.com> <2641105.1698788712@sss.pgh.pa.us> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sat, 2023-11-04 at 19:08 +0000, Abraham, Danny wrote: > Asking for help with a JDBC related issue. > Environment: Linux 7.9 PG 14.9 , very busy PG Server. >=20 > A big query - 3 unions and about 10 joins runs : > - 70ms on psql , DBeaver with JDBC 42 and in our Server using old JDBC = 9.2 > - 2500 ms in our Server using new JDBC 42 driver. ( and this is running = many times)=20 >=20 > Question: Is there a structured way to identify optimization setup ( Plan= ner Method s ) changes? > Are there any known changes specific to JDBC 42.=20 What I would do is enable auto_explain and look at the execution plan when the statement is run by the JDBC driver. Then you can compare the execution plans and spot the difference. Yours, Laurenz Albe