| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, fabriziomello(at)gmail(dot)com, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal "VACUUM SCHEMA" |
| Date: | 2014-12-22 17:17:33 |
| Message-ID: | 20141222171733.GH3062@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Andres Freund (andres(at)2ndquadrant(dot)com) wrote:
> On 2014-12-22 12:12:12 -0500, Stephen Frost wrote:
> > We might end up turning the autovacuum process into a generalized
> > scheduler/cron-like entity that way though.
>
> I'm not talking about autovacuum, just plain vacuumdb.
Oh, right, clearly I was thinking of autovacuum. Adding an option like
that to vacuumdb would certainly be a lot more straight-forward.
> > I'd rather we just build
> > that. Users would then be able to run a script periodically which
> > would add VACUUM commands to be run on whichever tables they want to
> > the jobs queue, either for immediate execution or at whatever time they
> > want (or possibly chronically :).
>
> And this discussion just feature creeped beyond anything realistic... :)
Yeah, but I really *want* this... ;)
Thanks!
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2014-12-22 17:17:56 | Re: pgbench -f and vacuum |
| Previous Message | Alvaro Herrera | 2014-12-22 17:17:15 | Re: Proposal "VACUUM SCHEMA" |