| From: | Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Andres Freund <andres(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal "VACUUM SCHEMA" |
| Date: | 2014-12-22 17:23:07 |
| Message-ID: | CAFcNs+p=pNGcT+MT4DVCL3b=xjH++RaQrZPKw8OW0LK86tbX0g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Dec 22, 2014 at 3:17 PM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
wrote:
>
> Stephen Frost wrote:
> > * Andres Freund (andres(at)2ndquadrant(dot)com) wrote:
>
> > > There's one argument for supporting more for VACUUM than the rest - it
> > > can't be executed directly as the result of a query as the others
> > > can... I wonder if that'd not better be answered by adding a feature
to
> > > vacuumdb that allows selecting the to-be-vacuumed table by a user
> > > defined query.
> >
> > Wow. That's certainly an interesting idea.
>
> +1.
>
Then to simplify can we allow the "--table" option of vacuumdb act similar
to the "--table" option of pg_dump??
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog: http://fabriziomello.github.io
>> Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
>> Github: http://github.com/fabriziomello
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2014-12-22 17:38:12 | Re: pgbench -f and vacuum |
| Previous Message | Tomas Vondra | 2014-12-22 17:17:56 | Re: pgbench -f and vacuum |