From: John R Pierce <pierce@hogranch.com>
To: PostgreSQL <pgsql-general@postgresql.org>
Subject: Re: partitioning
Date: Fri, 10 Aug 2012 18:27:11 -0700
Message-ID: <5025B4EF.4080303@hogranch.com> (raw)
In-Reply-To: <14FC3FAC-5DE7-44A0-BDCB-4916F196B6FD@codepuppy.com>
References: <5025AD10.5030004@hogranch.com>
<14FC3FAC-5DE7-44A0-BDCB-4916F196B6FD@codepuppy.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: pierce@hogranch.com
Subject: Re: partitioning
In-Reply-To: <5025B4EF.4080303@hogranch.com>
References: <5025AD10.5030004@hogranch.com> <14FC3FAC-5DE7-44A0-BDCB-4916F196B6FD@codepuppy.com> <5025B4EF.4080303@hogranch.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox