Re: Proposal "VACUUM SCHEMA"

From: Oskari Saarenmaa <os(at)ohmu(dot)fi>
To: fabriziomello(at)gmail(dot)com, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Proposal "VACUUM SCHEMA"
Date: 2014-12-28 15:38:45
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

21.12.2014, 18:48, Fabrízio de Royes Mello kirjoitti:
> I work with some customer that have databases with a lot of schemas and
> sometimes we need to run manual VACUUM in one schema, and would be nice
> to have a new option to run vacuum in relations from a specific schema.
> The new syntax could be:
> VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] { [ table_name ] | SCHEMA
> schema_name }
> Also I'll add a new option to "vacuumdb" client:
> -S, --schema=SCHEMA
> I can work on this feature to 2015/02 CF.
> Thoughts?

This would be useful for ANALYZE to make it easier to run analyze only
for the interesting schemas after a pg_upgrade. I have a database with
most of the actively used data in the "public" schema and a number of
rarely accessed large logging and archive tables in other schemas. It'd
be useful to prioritize analyzing the main tables before doing anything
about the rarely used schemas to allow the database to be put back into
production as soon as possible.

/ Oskari

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2014-12-28 20:37:05 Re: 9.5: Better memory accounting, towards memory-bounded HashAgg
Previous Message Michael Paquier 2014-12-28 15:15:03 Re: Patch: add recovery_timeout option to control timeout of restore_command nonzero status code