Re: Problems Vacuum'ing

From: jseymour(at)LinxNet(dot)com (Jim Seymour)
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Problems Vacuum'ing
Date: 2004-04-02 19:51:30
Message-ID: 20040402195130.B9AF04307@jimsun.LinxNet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> On Fri, Apr 02, 2004 at 12:02:22PM -0500, Jim Seymour wrote:
>
> [...]
>
> > Which is all well-and-good (tho, my ignorance readily conceded, four
> > minutes seems a mite... long), *except*: If I shut-down the
> > WebObjects application which, again, never accesses the db in
> > question, much-less any of its tables, this "time-out" doesn't seem
> > to apply. (I tried it.)
>
> 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.

> ISTM it would only matter when you try
> to vacuum a shared table, which this is not ...

That's what I would've thought.

Thanks for the follow-up. I was beginning to wonder if anybody'd
noticed ;).

Jim

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2004-04-02 20:35:03 Re: Problems Vacuum'ing
Previous Message Tom Lane 2004-04-02 19:48:13 Re: [GENERAL] Large DB