| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Julie Nishimura <juliezain(at)hotmail(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: is it safe to drop 25 tb schema with cascade option? |
| Date: | 2019-09-19 21:34:27 |
| Message-ID: | d0c2055d-1fe1-2e03-9d7a-9c4820b81bd3@aklaver.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 9/19/19 2:24 PM, Julie Nishimura wrote:
> Adrian,
> We do run vacuum w/o FULL every day:
> SYSTABLES="' pg_catalog.' || relname || ';' from pg_class a,
> pg_namespace b where a.relnamespace=b.oid and b.nspname='pg_catalog' an
> d a.relkind='r'"
>
> But it does not look like it frees up the space...
>
> Or you meant we need to run vacuum on 'my_db_name' without parameters,
> that it runs for every table? I am just not sure how long it will take
> to run for 39 tb...:(
Should have added to previous post that in this link:
https://www.postgresql.org/docs/8.2/routine-vacuuming.html#VACUUM-FOR-WRAPAROUND
there are some queries that can will show you the XID status for tables
and the database.
>
> Thanks
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-09-19 21:42:55 | Re: is it safe to drop 25 tb schema with cascade option? |
| Previous Message | Adrian Klaver | 2019-09-19 21:31:22 | Re: is it safe to drop 25 tb schema with cascade option? |