aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gin/ginarrayproc.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2011-09-02 14:29:31 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2011-09-02 14:29:31 -0400
commit5b562644fec696977df4a82790064e8287927891 (patch)
tree3f8132a4e7e9fb9591c3e7f069035388918ae020 /src/backend/access/gin/ginarrayproc.c
parent2f72d5df6a876406cf5f2f8d7800d591dff3e2e3 (diff)
downloadpostgresql-5b562644fec696977df4a82790064e8287927891.tar.gz
postgresql-5b562644fec696977df4a82790064e8287927891.zip
Teach ANALYZE to clear pg_class.relhassubclass when appropriate.
In the past, relhassubclass always remained true if a relation had ever had child relations, even if the last subclass was long gone. While this had only marginal performance implications in most cases, it was annoying, and I'm now considering some planner changes that would raise the cost of a false positive. It was previously impractical to fix this because of race condition concerns. However, given the recent change that made tablecmds.c take ShareExclusiveLock on relations that are gaining a child (commit fbcf4b92aa64d4577bcf25925b055316b978744a), we can now allow ANALYZE to clear the flag when it's no longer relevant. There is no additional locking cost to do so, since ANALYZE takes ShareExclusiveLock anyway.
Diffstat (limited to 'src/backend/access/gin/ginarrayproc.c')
0 files changed, 0 insertions, 0 deletions