Hi,
I need your help/suggestions with a problem I am facing related to autovacuum.
I am using PostgreSQL 8.1.2 through a JDBC connection. The connection is
long lived (established when the application starts up and is closed only when
the application is shutdown).
I have enabled the autovacuu
> Well, you need to work out why they are unremovable. For example, do
> you have any really long lived open transactions. These are generally a
> bad idea, for all sorts of reasons. If you don't commit occasionally,
> none of your changes will be visible to anyone else.
I have multiple databases
> >
> > Thanks again. I am wondering as to why the state changes to "Transaction in
> > idle" when a query is executed. It'll be nice if that happens only when
> > a real change is made (transaction starts) to the database and not when
> > a select query occurs.
>
> This makes no sense. A select
I haven't had issues about the max_fsm_pages. The problem I had was caused
because I was not committing (or rolling back) after JDBC select calls.
I didn't think that was necessary because the select calls didnt modify
database. But, once I modified my selects to rollback after the
data is read fro
