From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Greg Smith <greg(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: More vacuum stats |
Date: | 2010-08-23 14:46:15 |
Message-ID: | 20822.1282574775@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Mon, Aug 23, 2010 at 16:38, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>>> We could also store last_autovacuum_vacuum_duration - is that better
>>> or worse than start and end time?
>>
>> No, I think you want to know the actual time not only the duration.
> Well, you could calculate one from the other - especially if one takes
> less size, per your comment above.
With alignment considerations, adding a field is going to cost 8 bytes;
whether it's a timestamp or a duration isn't going to matter. I'd be
inclined to store the timestamp, it just seems more like the base datum.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-08-23 15:09:09 | Re: [BUGS] BUG #5305: Postgres service stops when closing Windows session |
Previous Message | Pavel Stehule | 2010-08-23 14:41:31 | Re: patch (for 9.1) string functions |