On Fri, Apr 02, 2004 at 02:51:30PM -0500, Jim Seymour wrote:
> >
> > On Fri, Apr 02, 2004 at 12:02:22PM -0500, Jim Seymour wrote:
> > Ok, so the WebObjects app keeps an idle open transaction? (i.e. it
> > issues a BEGIN as soon as the previous transaction is finished.) I'm not
> > sure I read the code correctly --
>
> I really couldn't say. I don't know what the WebObjects app is
> doing. I know, or *believe* I know, it's only doing queries. (It
> may be doing temp tables internally, or some-such.) Its interface
> to pgsql is via the JDBC that comes with pgsql. I don't know what
> the Java code it generated looks like.
Turn on query logging and see if the BEGIN is issued right after the
COMMIT/ROLLBACK, or whether it waits and issues it right before
SELECT/CREATE TEMP TABLE.
It doesn't matter if it's only doing queries; if it does them inside a
transaction, it would be enough to keep VACUUM from working "properly."
--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"La gente vulgar solo piensa en pasar el tiempo;
el que tiene talento, en aprovecharlo"
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
