Re: Postgres jdbc driver inconsistent behaviour with double precession

From: Dave Cramer <davecramer(at)postgres(dot)rocks>
To: Rahul Uniyal <rahul(dot)uniyal00(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Postgres jdbc driver inconsistent behaviour with double precession
Date: 2024-03-19 09:52:35
Message-ID: CADK3HH+hbeue82P1AAtroKeCCGXErUmYpqPRGvHin9EeT5c7Tg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Dave Cramer 2024-03-19 11:39:06 Re: Postgres jdbc driver inconsistent behaviour with double precession
Previous Message Hayato Kuroda (Fujitsu) 2024-03-19 04:39:30 RE: Potential data loss due to race condition during logical replication slot creation