Re: Postgres jdbc driver inconsistent behaviour with double precession

Thanks Dave for the much needed help. Thank you so much .

I am using binaryTransferDisable=FLOAT8 to resolve this problem.

Thanks 

Rahul 

On 19-Mar-2024, at 5:09 PM, Dave Cramer <davecramer(at)postgres(dot)rocks> wrote:



On Tue, 19 Mar 2024 at 06:55, Rahul Uniyal <rahul(dot)uniyal00(at)gmail(dot)com> wrote:

Thanks Dave for this much needed information.

I checked with by giving prepareThreshold = 0 it is working as expected . 

Also I tried another solution which is also working . 

I am setting binaryTransferDisable=FLOAT8 in the connection url and this seems also working fine . 

Is this approach is also recommended? 

This might be better as it will retain the prepared statement behaviour for all the other types.


P.S. please reply all so that others see the answers.

Dave 

Thanks ,


Rahul 

On 19-Mar-2024, at 3:22 PM, Dave Cramer <davecramer(at)postgres(dot)rocks> wrote:



On Mon, 18 Mar 2024 at 23:11, Rahul Uniyal <rahul(dot)uniyal00(at)gmail(dot)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