Re: Postgres jdbc driver inconsistent behaviour with double precession - Mailing list pgsql-bugs

From Dave Cramer
Subject Re: Postgres jdbc driver inconsistent behaviour with double precession
Date
Msg-id CADK3HH+hbeue82P1AAtroKeCCGXErUmYpqPRGvHin9EeT5c7Tg@mail.gmail.com
Whole thread Raw
In response to Re: Postgres jdbc driver inconsistent behaviour with double precession  (Dave Cramer <davecramer@postgres.rocks>)
List pgsql-bugs


On Mon, 18 Mar 2024 at 23:11, Rahul Uniyal <rahul.uniyal00@gmail.com> wrote:

Thanks Dave,

1- Is there any performance impact with this change ? As we have lot of double precession fields.

Well the reason we do it is for performance. It saves a round trip, but it costs one to get the info we need. So all in all it has minimal impact on pefrormance 

2- This prepareThreshold=0 property should be pass through connection url ? 

Yes

Dave

pgsql-bugs by date:

Previous
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: Potential data loss due to race condition during logical replication slot creation
Next
From: Dave Cramer
Date:
Subject: Re: Postgres jdbc driver inconsistent behaviour with double precession