It's not a fault of the JDBC driver, you're right that it won't hold open a
transaction ... it's with my application server ... which, i unfortunately
don't have control over ... for some reason it seems to keep all of its
connections in an open transaction ...
the really mysterious part is the way that it has always been ... and prior
to my upgrade to 7.2.1, i ran a vacuum and a reindex every night and the
space was reclaimed ... that's what brought this whole thing on ...
something has changed ...
-dave
> -----Original Message-----
> From: pgsql-general-owner@postgresql.org
> [mailto:pgsql-general-owner@postgresql.org]On Behalf Of Andrew Sullivan
> Sent: Tuesday, April 09, 2002 3:41 PM
> To: PostgreSQL general list
> Subject: Re: [GENERAL] vacuuming not working?
>
>
> On Mon, Apr 08, 2002 at 05:35:58PM -0400, Tom Lane wrote:
> > "David Esposito" <dvesposito@newnetco.com> writes:
>
> > > if so, is there anything that i can do about it ... (yes, i
> > > suppose i need to figure out why the JDBC connections have
> transactions
> > > started before they're actually needed) ...
> >
> > Darn if I know. You might try asking pgsql-jdbc list.
>
> I _believe_ this is a feature of the autocommit=off setting. I think
> you can turn autocommit on and start and end your transactions
> yourself. Check the docs, though -- I've been shown to have faulty
> memory.
>
> A
>
> --
> ----
> Andrew Sullivan 87 Mowat Avenue
> Liberty RMS Toronto, Ontario Canada
> <andrew@libertyrms.info> M6K 3E3
> +1 416 646 3304 x110
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)