| From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
|---|---|
| To: | Jorge Solórzano <jorsol(at)gmail(dot)com> |
| Cc: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>, Malcolm Studd <malcolm(dot)studd(at)tradingcentral(dot)com>, List <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: postgresql-jdbc driver not respecting prepareThreshold=0 |
| Date: | 2017-02-03 13:56:09 |
| Message-ID: | CADK3HHKKApfgiJr6T3EDom8N=L_u_eAfWsFi8tjcU3H++QfiEw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On 3 February 2017 at 08:53, Jorge Solórzano <jorsol(at)gmail(dot)com> wrote:
>
> On Fri, Feb 3, 2017 at 6:30 AM, Dave Cramer <pg(at)fastcrypt(dot)com> wrote:
>
>>
>> On 3 February 2017 at 07:16, Vladimir Sitnikov <
>> sitnikov(dot)vladimir(at)gmail(dot)com> wrote:
>>
>>
>>> TL;DR: I suggest to review "feat: use java.util.logging", test it, merge
>>> it and release the resulting artifact as pgjdbc 42.0.0
>>>
>>> Are there any concerns regarding that plan?
>>>
>>> I haven't had a good look at it. Does the old way of enabling it work ?
>> Does anyone care ?
>>
>
>
> Hi Dave, the old way of enabling it do not work. Maybe we can start a new
> thread
>
> asking if anyone care, I really hope that nobody cares, since it have
> the potential of break compatibility if someone is using the old way for
> something more than debug localy.
>
Sorry for not looking this up myself, but have you provided an updated
documentation patch then ?
Dave Cramer
davec(at)postgresintl(dot)com
www.postgresintl.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jorge Solórzano | 2017-02-03 14:16:30 | Re: postgresql-jdbc driver not respecting prepareThreshold=0 |
| Previous Message | Jorge Solórzano | 2017-02-03 13:53:06 | Re: postgresql-jdbc driver not respecting prepareThreshold=0 |