Re: Why our counters need to be time-based WAS: WIP: cross column correlation ...
От | Tom Lane |
---|---|
Тема | Re: Why our counters need to be time-based WAS: WIP: cross column correlation ... |
Дата | |
Msg-id | 27252.1298919003@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Why our counters need to be time-based WAS: WIP: cross column correlation ... (Josh Berkus <josh@agliodbs.com>) |
Ответы |
Re: Why our counters need to be time-based WAS: WIP: cross
column correlation ...
Re: Why our counters need to be time-based WAS: WIP: cross column correlation ... |
Список | pgsql-hackers |
Josh Berkus <josh@agliodbs.com> writes: > On 2/28/11 10:24 AM, Robert Haas wrote: >> On Mon, Feb 28, 2011 at 1:04 PM, Josh Berkus <josh@agliodbs.com> wrote: >>> On the other hand, anything which increases the size of pg_statistic >>> would be a nightmare. >> Hmm? > Like replacing each statistic with a series of time-based buckets, which > would then increase the size of the table by 5X to 10X. That was the > first solution I thought of, and rejected. I think Josh is thinking of the stats collector's dump file, not pg_statistic. Ultimately we need to think of a reporting mechanism that's a bit smarter than "rewrite the whole file for any update" ... regards, tom lane
В списке pgsql-hackers по дате отправления: