From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | 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 22:37:28 |
Message-ID: | 38e75ba0-65f1-0455-adc1-c906c3a7c4b6@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 9/19/19 4:55 PM, Tom Lane wrote:
> Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> writes:
>> So this is the part I need some clarification on. If you start vacuuming
>> the tables that are setting the min then that should buy you some time?
> Yes, if there are some small tables that have relfrozenxid even further
> back than the big ones, vacuuming them first would be a win.
With this?
CDSCH02=# select cl.oid,
COALESCE(ta.schemaname, 'pg_toast'),
cl.relname,
cl.relfrozenxid,
age(cl.relfrozenxid)
from pg_class cl FULL JOIN pg_tables ta
ON ta.tablename = cl.relname
where not cl.relfrozenxid = xid '0'
order by age(cl.relfrozenxid) desc
;
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | rob stone | 2019-09-20 01:45:11 | Re: PGPASSWORD in crypted form, for example BlowFish or SHA-256 |
Previous Message | Tom Lane | 2019-09-19 21:55:27 | Re: is it safe to drop 25 tb schema with cascade option? |