| From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: drop database |
| Date: | 2019-10-17 23:55:53 |
| Message-ID: | 1cc3f4c8-aa8e-0e0b-3f02-841da307bffb@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
There are other databases in the cluster.
On 10/17/19 5:12 PM, Andrew Kerber wrote:
> If you are decommissioning the database, why not just rm -rf the whole system?
>
> On Thu, Oct 17, 2019 at 4:31 PM Michael Lewis <mlewis(at)entrata(dot)com
> <mailto:mlewis(at)entrata(dot)com>> wrote:
>
> Your plan to loop over tables and truncate them seems great if you are
> worried. It seems simple to verify that space is being freed as you
> go, and also easy to change tactics if the need arises.
>
>
--
Angular momentum makes the world go 'round.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | chris | 2019-10-18 01:20:57 | Re:Using PostgreSQL for Machine Learning Data Pipelines |
| Previous Message | Adrian Klaver | 2019-10-17 23:41:58 | Re: stable for each row before insert trigger |