| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com> |
| Cc: | Ron <ronljohnsonjr(at)gmail(dot)com>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Determine potential change in table size after a column dropped? |
| Date: | 2022-01-22 17:27:11 |
| Message-ID: | CAKFQuwYRadodYVeoK3e1oZ8q=rRVCxDT89HVMADt87HDXK8YWQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Sat, Jan 22, 2022 at 10:09 AM Wells Oliver <wells(dot)oliver(at)gmail(dot)com>
wrote:
> I need only drop the column and VACUUM FULL the table, and not the entire
> DB, right?
>
Do you seriously think that vacuuming the entire database is a
possible requirement here?
In terms of estimated space savings, the data type documentation tells you
how much space each data type consumes. A reasonable first estimate,
knowing nothing else about the internals of the system, is to multiply that
by the number of rows. That would provide a lower-bound estimate. If that
amount makes the effort worth it then no further info is needed.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Khushboo Vashi | 2022-01-24 04:34:42 | Re: PGAdmin - psql tool issue |
| Previous Message | Wells Oliver | 2022-01-22 17:08:31 | Re: Determine potential change in table size after a column dropped? |