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 1sI5br-00CwxZ-ET for pgsql-jdbc@arkaria.postgresql.org; Fri, 14 Jun 2024 12:00:47 +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 1sI5bp-000AI7-5x for pgsql-jdbc@arkaria.postgresql.org; Fri, 14 Jun 2024 12:00:46 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sI5bo-000AHz-Ui for pgsql-jdbc@lists.postgresql.org; Fri, 14 Jun 2024 12:00:45 +0000 Received: from mail-yb1-xb32.google.com ([2607:f8b0:4864:20::b32]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sI5bn-001dAH-5Y for pgsql-jdbc@lists.postgresql.org; Fri, 14 Jun 2024 12:00:45 +0000 Received: by mail-yb1-xb32.google.com with SMTP id 3f1490d57ef6-dff0067a263so2384812276.0 for ; Fri, 14 Jun 2024 05:00:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1718366441; x=1718971241; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=YGORsUereekTIXSVxy1uFyenEVtMZIAvOyUACFQxFYo=; b=JnAsxSiBOfbRsUU2VYGeaBnKj15LEBg/hwOhx6EVnEzR5BdpyD6m+OdFcJR7+lYL6N rk2X647xxvXMIj59sddMQRDLvoqEMJhWnR8+SPit0YZSYjvEJHrg86GNxExwJFFgFn3x lrk8gz/CYkORm+lnCyTf+XZMqlVa8oJs66YhFmZgLKCRrtJehGvHnHUFeb6kybb2mzk4 sOYq5KQn9wdHKMO1s4mEqeyszaJxVfeYLcjCP3r4hYKYmOP/T6IGhDjOoFnRL2lEAUN+ chA9RGBxGpeR8roCv177xLtoKXtr3zHMoMOhlyXczS9id0tkBPGpbjfAocAlsfpIrUTG layA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718366441; x=1718971241; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=YGORsUereekTIXSVxy1uFyenEVtMZIAvOyUACFQxFYo=; b=kRamECFwxwSwhruzutKrGebOZgLgGG5nPH/qMWKxG95X2plD5OsoSHY8hs6PGFSzW8 P0yUJmfx+lQBi8fM0vF5/7sfhkLYqmHlk8I5WuTBBEX8C8xfz4QY8qEbdWJOJC9k+FP1 ueEanNgZLGT559aWX6A/BYzeMziRsEP+NLXHetKQ+ou01ysD1g3oTnk/SXaup/MwKZvr LDKXOdbFbWgAgY22nRJthPipkSwtNSj4EvzYkXVXSCzfwBYPw4/HAJMdZ2I6KF3Olzg0 TJ8JNhXaoKWlxT16MDNbbIdKf9XFWYhm7YmElg7wq/NDqLjKVYnisJjh+8zrBuXuOLTD Wu4w== X-Gm-Message-State: AOJu0YwBZOBy9zscjdshVhtk6F8SY/KVYWst7m2CaKkchN3oSAIN/KDu bS5IpkTa0l5HdPqGMdU9iIf3ZyKTP6GgcZNH1kGO93uJMXVxgIK0imJd1HY9nVQnRlsdd/siuvr QP+5DgDbpwbJQNgnY+KBMVMrO7I4HtqNVKPI= X-Google-Smtp-Source: AGHT+IF6qNpGWbqVYDDNzvp/d+KjMRVRkyobsYdDN+MzQWVCTWJgZZwyc93x51VIPDEmDPWmK/Fx/6O6f5Ece057caU= X-Received: by 2002:a25:2e4e:0:b0:dfa:ccb2:b18 with SMTP id 3f1490d57ef6-dff153422ddmr2312616276.6.1718366441366; Fri, 14 Jun 2024 05:00:41 -0700 (PDT) MIME-Version: 1.0 From: charles Lgn Date: Fri, 14 Jun 2024 14:00:30 +0200 Message-ID: Subject: Postgres explain plan is not correctly optimezed if the data is a "double" but the collumn is a "numeric" To: pgsql-jdbc@lists.postgresql.org Content-Type: multipart/alternative; boundary="00000000000054f426061ad85dd5" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000054f426061ad85dd5 Content-Type: text/plain; charset="UTF-8" Hello, I opened a pull request on the postgres jdbc, because the execution plan could be false when calculating, leading to performance issues. There's more on the subject here : https://github.com/pgjdbc/pgjdbc/pull/3285 thank you in advance Charles --00000000000054f426061ad85dd5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello,

I opened a pull request on the p= ostgres jdbc, because the execution plan could be false when calculating, l= eading to performance issues.

There's more on = the subject here :=C2=A0https://github.com/pgjdbc/pgjdbc/pull/3285

thank you in advance
Charles
--00000000000054f426061ad85dd5--