| From: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Catalog bloat (again) |
| Date: | 2016-01-27 23:02:00 |
| Message-ID: | 20160127230200.GQ17113@anvilwalrusden.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Jan 27, 2016 at 11:54:37PM +0100, Ivan Voras wrote:
> So, question #1: WTF? How could this happen, on a regularly vacuumed
> system? Shouldn't the space be reused, at least after a VACUUM? The issue
> here is not the absolute existence of the bloat space, it's that it's
> constantly growing for *system* tables.
Some system tables (particularly pg_attribute) are heavily changed by
a lot of temp table use. You need to amp up the vacuum frequency on
them, and have a lot of workers, or you don't get to them until it's
too late.
> Question #2: What can be done about it?
You may end up taking an outage in effect, because you need to compact
them at least once. If you can flip to a replica, that is the easiest
way to fix it.
A
--
Andrew Sullivan
ajs(at)crankycanuck(dot)ca
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Don Parris | 2016-01-27 23:03:10 | Re: Multi-Table Insert/Update Strategy - Use Functions/Procedures? |
| Previous Message | David G. Johnston | 2016-01-27 22:59:46 | Re: A contradiction in 13.2.1 |