From: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
---|---|
To: | jim(at)contactbda(dot)com |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Recording vacuum/analyze/dump times |
Date: | 2005-03-07 21:15:45 |
Message-ID: | 422CC481.5010503@zeut.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Right, once autovacuum is integrated, then I think vacuum and analyze
should update the autovacuum table this way autovacuum won't redundantly
vacuum tables that were just vacuumed manually.
Jim Buttafuoco wrote:
>But what happens if I go in and manually vacuum a table (either because I just deleted a bunch of records or whatever).
> This is why I think the backend should record the date in pg_class.
>
>
>---------- Original Message -----------
>From: "Matthew T. O'Connor" <matthew(at)zeut(dot)net>
>To: jim(at)contactbda(dot)com
>Cc: pgsql-hackers(at)postgresql(dot)org
>Sent: Mon, 07 Mar 2005 13:56:04 -0500
>Subject: Re: [HACKERS] Recording vacuum/analyze/dump times
>
>
>
>>Jim Buttafuoco wrote:
>>
>>
>>
>>>Its there a reason postgresql doesn't record vacuum/analyze and dump times in pg_class (or another table). This seems
>>>like it would be a very helpful feature.
>>>
>>>for pg_dump I would add an option --record=YES|NO
>>>for vacuum and analyze I would add a NORECORD|RECORD option
>>>
>>>
>>>
>>>
>>For what it's worth, integrated pg_autovacuum will have something like
>>this. At least my initial design does, since the autovacuum daemon
>>needs to know remember when the last time a table was vacuumed.
>>
>>
>------- End of Original Message -------
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Buttafuoco | 2005-03-07 21:46:58 | Re: Recording vacuum/analyze/dump times |
Previous Message | Tom Lane | 2005-03-07 19:09:11 | Re: About b-tree usage |