| From: | xu jian <jamesxu(at)outlook(dot)com> |
|---|---|
| To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | how to shrink pg_attribute table? |
| Date: | 2017-05-10 02:10:28 |
| Message-ID: | MWHPR20MB15682463D716C9435EFFDE8EA1EC0@MWHPR20MB1568.namprd20.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello,
My application creates temp table frequently. Now I find pg_attribute table is growing larger and larger, 90GB now.
pgstattuple shows 82% free space, so I restored the db to dev env, and tried vacuum full to shrink it.
However, the vacuum full run for 24 hours, and hang there. I can see a CPU is on 100% usage, no disk activity.
looks like a bug of vacuum full. my pg version is 9.6.1. auto_vacuum uses default value.
Does anyone has this issue before? how to shrink the pg_attribute table? and what is the best configuration for auto_vacuum parameter? thanks
James
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2017-05-10 02:31:14 | Re: transition table behavior with inheritance appears broken (was: Declarative partitioning - another take) |
| Previous Message | Vaishnavi Prabakaran | 2017-05-10 01:51:28 | Removal of plaintext password type references |