From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Lance Luvaul <lance(dot)luvaul(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Full list of operations that constitute a "maintenance" operation? |
Date: | 2018-11-09 10:39:28 |
Message-ID: | a0d0d76db1614513b54f965062d194a5cc8c7613.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Lance Luvaul wrote:
> Hi all, I've read on the Postgres documentation for 'maintenance_work_mem' that VACUUM, CREATE INDEX,
> and ALTER TABLE ADD FOREIGN KEY are considered maintenance operations, but are there others?
> For example I use ALTER TABLE ADD COLUMN and ALTER TABLE SET LOGGED in my scripts...
> are they maintenance operations that would cause a maintenance_work_mem-sized chunk of memory
> (or more than 1 such chunk) to be allocated? Is there a complete list somewhere? Thanks!
Trawling the source shows that it is used for index operations like CREATE INDEX and REINDEX,
but also for ALTER TABLE ADD FOREIGN KEY, VACUUM and CLUSTER.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Westermann | 2018-11-09 12:58:17 | index only scan question |
Previous Message | Adrien NAYRAT | 2018-11-09 10:33:12 | Re: ERROR: found multixact from before relminmxid |