| From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | Euler Taveira <euler(at)timbira(dot)com(dot)br>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Should the docs have a warning about pg_stat_reset()? |
| Date: | 2019-04-14 17:33:12 |
| Message-ID: | 20190414173312.gol4vydyixgjtuc5@development |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Apr 14, 2019 at 09:11:52AM -0500, Joe Conway wrote:
>On 4/13/19 3:42 PM, Tomas Vondra wrote:
>> If only we had a way to regularly snapshot the data from within the
>> database, and then compute the deltas on that. If only we could insert
>> data from one table into another one a then do some analysics on it,
>> with like small windows moving over the data or something ...
>
>Why not store deltas separately with their own delta reset command?
>
Well, we could do that, but we don't. Essentially, we'd implement some
sort of RRD, but we'd have to handle cleanup, configuration (how much
history, how frequently to snapshot the deltas). I think the assumption
is people will do that in a third-party tool.
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-04-14 17:38:56 | Re: hyrax vs. RelationBuildPartitionDesc |
| Previous Message | Alvaro Herrera | 2019-04-14 17:32:14 | Re: pg_dump is broken for partition tablespaces |