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 1kY8V8-0006Ek-Ny for pgsql-bugs@arkaria.postgresql.org; Thu, 29 Oct 2020 14:02:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kY8V7-00010W-G7 for pgsql-bugs@arkaria.postgresql.org; Thu, 29 Oct 2020 14:02:01 +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 1kY8V7-00010P-AA for pgsql-bugs@lists.postgresql.org; Thu, 29 Oct 2020 14:02:01 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kY8V5-0007SX-5b for pgsql-bugs@lists.postgresql.org; Thu, 29 Oct 2020 14:02:00 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 09TE1qSt1513987; Thu, 29 Oct 2020 10:01:53 -0400 From: Tom Lane To: Hetty Kronemeijer cc: "pgsql-bugs@lists.postgresql.org" Subject: Re: spring context cannot load when I use postgres 42.2.15 or higher In-reply-to: References: Comments: In-reply-to Hetty Kronemeijer message dated "Thu, 29 Oct 2020 12:34:58 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1513985.1603980112.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Thu, 29 Oct 2020 10:01:52 -0400 Message-ID: <1513986.1603980112@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hetty Kronemeijer writes: > My spring application was using postgres driver version 42.2.16. > Recently I added jpa using spring-boot-data-jpa version 2.3.1.RELEASE, a= nd spring version 5.2.7.RELEASE. > Loading the spring context results in and error now. This happens with a= ll versions of postgres from 42.2.15. You might have better luck asking about this on the pgsql-jdbc@lists.postgresql.org mailing list. This list is mostly for issues with the core Postgres server, which I don't think this is. regards, tom lane