| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Gilles Darold <gilles(at)migops(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [Proposal] vacuumdb --schema only |
| Date: | 2022-03-04 10:56:40 |
| Message-ID: | 20220304105639.GJ27651@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Mar 04, 2022 at 10:11:28AM +0100, Gilles Darold wrote:
> The attached patch implements that. Option -n | --schema can be used
> multiple time and can not be used together with options -a or -t.
Yes, thanks.
I suggest there should also be an --exclude-schema.
> I do not propose to extend the VACUUM and ANALYZE commands because their
> current syntax doesn't allow me to see an easy way to do that
I think this would be easy with the parenthesized syntax.
I'm not suggesting to do it there, though.
> + /*
> + * When filtereing on schema name, filter by table is not allowed.
> + * The schema name can already be set in a fqdn table name.
set *to*
--
Justin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dinesh Chemuduru | 2022-03-04 11:27:56 | Re: [Proposal] vacuumdb --schema only |
| Previous Message | Thomas Munro | 2022-03-04 10:50:46 | Re: Regression tests failures on Windows Server 2019 - on master at commit # d816f366b |