"Boguk Maxim" <maxim.bo...@gmail.com> writes:
> When transaction which used TEMP table with ON COMMIT DELETE ROWS commit or
> rollback pg_stats and pg_stat_all_tables about that temporary table doesn't
> reset.
> It's no problem with common applications but with pgbouncer + transaction
> pooling mode postgresql backends staying alive long time and incremental
> errors in statistic about temporary tables leading to choose insane query
> plans and bad performance in general.
With a temp table it's pretty much on your application's head to do
ANALYZE at appropriate times. There's no way for autovac to do it for
you. I don't see any point in creating strange corner-case behaviors
in the stats code given the fundamental need for manual ANALYZEs.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
