curious vacuum full behavior - Mailing list pgsql-general

From Zwettler Markus (OIZ)
Subject curious vacuum full behavior
Date
Msg-id d9e34b260bfe45b280005f6cdc2814f7@zuerich.ch
Whole thread Raw
Responses Re: curious vacuum full behavior  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-general

I have 2 identical systems A + B.

B being a clone of A.

 

 

The table pg_catalog.pg_largeobject was identical on both systems: 300GB in total size; 100GB bloated.

 

 

I did following on A:

ð  vacuum full pg_catalog.pg_largeobject;

(using the default maintenance_work_mem of 64MB)

It took around 45 minutes and increased the diskspace by around 125% until the vacuum had been finished.

 

 

I did following on B:

ð  set maintenance_work_mem = '256MB';

ð  vacuum full pg_catalog.pg_largeobject;

This took around 5 minutes. I don't know if the diskspace ever increased.

 

 

I was really surprised.

Is there any explanation on this behavior?

Is vacuum full heavily using on-disk sort areas if maintenance_work_mem is too low?

 

 

Postgres Version 9.6

 

 

Thanks, Markus

 

 

pgsql-general by date:

Previous
From: Adith Suresh
Date:
Subject: PgAdmin 4 GUI not responding
Next
From: Atul Kumar
Date:
Subject: vacuumdb not letting me connect to db