Re: Drop any statistics of table after it's truncated

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Drop any statistics of table after it's truncated
Дата
Msg-id 31233.1413296415@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Drop any statistics of table after it's truncated  (Sawada Masahiko <sawada.mshk@gmail.com>)
Ответы Re: Drop any statistics of table after it's truncated
Список pgsql-hackers
Sawada Masahiko <sawada.mshk@gmail.com> writes:
> I found that the statistics are still remained after it's truncated.
> In addition, the analyzing ignores table does not have any tuple.
> After table truncated, the entry of statistics continues to remain
> unless insertion and analyzing are executed.
> There is reason why statistics are remained?

Yes, actually, that's intentional.  The idea is that once you start
loading data into the table, it's most likely going to look something
like the old data; therefore, the stale statistics are better than
none at all.  Eventually auto-ANALYZE will replace the stats,
but until that happens, it seems best to keep using the old stats.
(Of course there are counterexamples to this, but removing the stats
is bad in more cases than not.)

> Attached patch is one line patch adds RemoveStatistics() into
> ExecuteTruncate(), to remove statistics entry of table.

-1, for the reasons explained above.
        regards, tom lane



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: Wait free LW_SHARED acquisition - v0.9
Следующее
От: Andres Freund
Дата:
Сообщение: Re: WIP: dynahash replacement for buffer table