| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | "Zwettler Markus (OIZ)" <Markus(dot)Zwettler(at)zuerich(dot)ch>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: AW: running vacuumlo periodically |
| Date: | 2021-01-29 19:12:10 |
| Message-ID: | 68f1b81a26a8ca96f1b64c673d4dfd6d903af5f6.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, 2021-01-29 at 15:44 +0000, Zwettler Markus (OIZ) wrote:
> I run "vacuumlo" in batches (-l) which worked well.
>
> I found table "pg_catalog.pg_largeobjects" to be massively bloated afterwards.
Sure, that deletes entries from that table.
> I tried "vacuum full pg_catalog.pg_largeobjects" but run out of diskspace (although having 250G diskspace free; database size = 400G).
>
> Question:
> Will "vacuum full pg_catalog.pg_largeobjects" need less diskspace when "maintenance_work_mem" is increased?
No, it won't. It will just be faster.
That sounds like your database consists almost exclusively of large objects...
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2021-01-29 19:14:19 | Re: Npgsql and the Connection Service File |
| Previous Message | Zwettler Markus (OIZ) | 2021-01-29 15:44:11 | AW: running vacuumlo periodically |