| From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: vacuum full doubled database size |
| Date: | 2020-03-13 17:36:39 |
| Message-ID: | 7c0a3bab-859e-5be4-f0bd-0e06d72f40de@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 3/13/20 10:32 AM, Fabio Ugo Venchiarutti wrote:
> On 13/03/2020 15:15, Ron wrote:
>> This is why I'd VACUUM FULL in a planned manner, one or two tables at a
>> time, and *locally* from crontab.
>
> That's not really viable on any remotely busy system: VACUUM FULL claims
> exclusive table locks, causing queries to hang
> (https://www.postgresql.org/docs/current/sql-vacuum.html#NOTES mentions
> this too).
This is of course *if* I were to ever do a VACUUM FULL... :)
The point is that your mother's rule about not sticking a giant fork-full of
food into your mouth is also an excellent rule in IT.
--
Angular momentum makes the world go 'round.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2020-03-13 19:17:02 | Re: encrypt/decrypt between javascript and postgresql. |
| Previous Message | Jerry Sievers | 2020-03-13 16:25:50 | Re: pg_upgrade 9.6 to 12 without 9.6 binaries |