From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Sridhar N Bamandlapally <sridhar(dot)bn1(at)gmail(dot)com> |
Cc: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: [ADMIN] How to drop stats on table |
Date: | 2015-11-21 21:45:03 |
Message-ID: | CAMkU=1xbFuuLFPfjJ_jtYEuEC1b00i3x2mjyczTK-UXDA+mHyA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general |
On Fri, Nov 20, 2015 at 11:24 PM, Sridhar N Bamandlapally
<sridhar(dot)bn1(at)gmail(dot)com> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Masaru Sugawara | 2015-11-22 14:33:44 | Re: 【楽天ブックス】お届けできなかった商品に関するお詫び |
Previous Message | Alexander Shereshevsky | 2015-11-21 17:19:23 | Re: [ADMIN] How to drop stats on table |
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Luya | 2015-11-22 09:54:16 | After configuring remote access,server can't be started |
Previous Message | Alexander Shereshevsky | 2015-11-21 17:19:23 | Re: [ADMIN] How to drop stats on table |