On Fri, Nov 20, 2015 at 11:24 PM, Sridhar N Bamandlapally <sridhar.bn1@xxxxxxxxx> wrote: > the actual issue is, when > > 1. temp table <say tmp1>is created with rows > 2. stats/analyze on table (tmp1) > 3. table dropped (tmp1) > > but in stats related catalog tables a blot is created > > In this scenario, thousands of temp tables created per day, blots are > increasing and stats related tables are growing to 10's of GB > > however, we schedule vacuum on catalog tables to control size > > the worry is, catalog tables also undergo MVCC concept > > I think when table is dropped, should have option to remove or reuse related > blot-space on catalog tables That should happen automatically, unless your server crashes often while the tables are in place, or you have encountered a bug. How reliably can you trigger the problem? And what version are you on? Cheers, Jeff -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
