On Mon, Sep 15, 2014 at 5:13 PM, Simon Riggs <si...@2ndquadrant.com> wrote: > On 15 September 2014 17:09, Robert Haas <robertmh...@gmail.com> wrote: >> Do we really want to disable HOT for all catalog scans? > > The intention of the patch is that catalog scans are treated > identically to non-catalog scans. The idea here is that HOT cleanup > only occurs on scans on target relations, so only INSERT, UPDATE and > DELETE do HOT cleanup. > > It's possible that many catalog scans don't follow the normal target > relation logic, so we might argue we should use HOT every time. OTOH, > since we now have separate catalog xmins we may find that using HOT on > catalogs is no longer effective. So I could go either way on how to > proceed; its an easy change either way.
What I'm thinking about is that the smarts to enable pruning is all in the executor nodes. So anything that updates the catalog without going through the executor will never be subject to pruning. That includes nearly all catalog-modifying code throughout the backend. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
