Re: vacuuming not working?

Hi,

1) Does your app server rollback/commit first then open a new transaction
and go idle?
2) Or does it rollback/commit then go idle. Then only begin when there's
something to do.
3) Or it goes idle after selects etc without rollback/commit.

As far as I know, 7.1.x vacuum in another connection will block for 3) but
not 1). I haven't tested 7.2.1 yet, but you can test 1) by opening up two
psql windows and doing a begin; select * from table; rollback; begin; and
then try vacuum in another. You can do similar tests for the other situations.

How do you do your vacuum and reindex?

Good luck!
Link.

At 04:19 PM 4/9/02 -0400, David Esposito wrote:
>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