Re: Small TRUNCATE glitch
От | Tom Lane |
---|---|
Тема | Re: Small TRUNCATE glitch |
Дата | |
Msg-id | 25100.1207261419@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Small TRUNCATE glitch (Alvaro Herrera <alvherre@commandprompt.com>) |
Ответы |
Re: Small TRUNCATE glitch
|
Список | pgsql-hackers |
Alvaro Herrera <alvherre@commandprompt.com> writes: > Tom Lane wrote: >> Just noticed that TRUNCATE fails to clear the stats collector's counts >> for the table. I am not sure if it should reset the event counts or >> not (any thoughts?) but surely it is wrong to not zero the live/dead >> tuple counts. > Agreed, the live/dead counters should be reset. Regarding event counts, > my take is that we should have a separate statement count for truncate > (obviously not a tuple count), and the others should be left alone. I thought some more about how to do it, and stumbled over how to cope with TRUNCATE being rolled back. That nixed my first idea of just having TRUNCATE send a zero-the-counters-now message. regards, tom lane
В списке pgsql-hackers по дате отправления: