| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Filho Arrais <arraisfilho(at)gmail(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Vacuum Full by Scheme |
| Date: | 2016-05-12 03:48:39 |
| Message-ID: | CAB7nPqQooABr8XZOPuwkhfWoFAXXnF+VdHY_gjNHi=v9dDLQqQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, May 12, 2016 at 7:31 AM, Filho Arrais <arraisfilho(at)gmail(dot)com> wrote:
> There is some development to use the vacuum full by scheme?
>
> Ex: vacuumdb -d postgres -parameter public
>
> In databases with thousands of tables and multiple scheme, it would be
> interesting to have this feature.
No that I know of. The only way to achieve that now is to use a script
that fetches the list of tables in schema first and runs VACUUM on
those tables individually, as VACUUM cannot be run in a stored
procedure.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-05-12 03:52:47 | Re: Perf Benchmarking and regression. |
| Previous Message | Etsuro Fujita | 2016-05-12 03:18:39 | Re: Use %u to print user mapping's umid and userid |