| From: | Anoop K <anoopk6(at)gmail(dot)com> |
|---|---|
| To: | John R Pierce <pierce(at)hogranch(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: REINDEX deadlock - Postgresql -9.1 |
| Date: | 2013-02-11 06:25:33 |
| Message-ID: | CADK_1hJLF7oJEg89-1-NL1i2=nmGY5W1j-Ey=pgYg4A-MQmWMQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Yes, we do that.
On Mon, Feb 11, 2013 at 11:53 AM, John R Pierce <pierce(at)hogranch(dot)com> wrote:
> On 2/10/2013 9:55 PM, Anoop K wrote:
>
> We analyzed the application side. It doesn't seem to be create a
> transaction and keep it open. StackTraces indicate that it is BLOCKED in
> JDBC openConnection.
>
> Any JDBC driver issue or other scenarios which can result in <*idle in
> transaction*> ?
>
>
> JDBC has a wretched habit of autostarting transactions on any query if the
> connection is not in autocommit mode. if you don't want to use autocommit
> mode, then you need to issue Commit() calls after each batch of queries,
> even if the queries are read only, to release any implied locks.
>
>
>
>
> --
> john r pierce 37N 122W
> somewhere on the middle of the left coast
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergey Konoplev | 2013-02-11 06:26:03 | Re: REINDEX deadlock - Postgresql -9.1 |
| Previous Message | John R Pierce | 2013-02-11 06:23:51 | Re: REINDEX deadlock - Postgresql -9.1 |