From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | KUNES Michael <Michael(dot)KUNES(at)frequentis(dot)com>, "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Mail an JDBC driver |
Date: | 2016-08-02 12:40:16 |
Message-ID: | CADK3HHJkXjjP+yf+74_nR-TzA-FR-1+ZwWzDysOtStKQ7CWw7A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Could be because we now cache statements. I suspect the cached statement
would not like you switching the schema out from under it.
How are you changing the search path? Ideally if you use setSchema we may
have to look at invalidating the cache. Vladimir ?
Dave Cramer
davec(at)postgresintl(dot)com
www.postgresintl.com
On 2 August 2016 at 08:27, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:
> On Tue, Aug 2, 2016 at 3:31 AM, KUNES Michael <
> Michael(dot)KUNES(at)frequentis(dot)com> wrote:
>
>> If you need more information, please let us know.
>>
>
> Is the same DB version (and which exact versions) being used in both
> tests? I strongly suspect no...
>
> Can you turn on full statement logging and see if anything unusual shows
> up?
>
> What's in your WHERE clause on the delete - and did you use Statement or
> PreparedStatement?
>
> Having a self-contained test case makes the previous two items less
> problematic. Also, that general test case can be translated to psql which
> would help to isolate the problem to either the driver or the database.
>
> David J.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | KUNES Michael | 2016-08-02 12:51:37 | Re: Mail an JDBC driver |
Previous Message | David G. Johnston | 2016-08-02 12:27:37 | Re: Mail an JDBC driver |