| From: | John R Pierce <pierce(at)hogranch(dot)com> |
|---|---|
| To: | PostgreSQL <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: partitioning |
| Date: | 2012-08-11 01:27:11 |
| Message-ID: | 5025B4EF.4080303@hogranch.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 08/10/12 6:00 PM, Jeff Potter wrote:
> Is it possible that you have any "idle in transaction" connections holding those tables open? See what you get when you show locks.
its very possible. the developer thought he'd fixed all those and was
surprised they were recurring. they are coming from JDBC by default
starting a transaction on a simple SELECT. we don't 'commit' after
selects as this code was written for Oracle, where plain selects dont
have side effects like this. this is only a problem in Postgres. the
intent is to use connections with 'autocommit on' for pure read
threads.... however, this is a very large and complex code base, and
site specific code is added by field engineering, so sometimes stuff
slips in.
--
john r pierce N 37, W 122
santa cruz ca mid-left coast
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dan Halbert | 2012-08-11 03:32:35 | select distinct in a subquery bug/problem |
| Previous Message | John R Pierce | 2012-08-11 00:53:36 | partitioning |