]> granicus.if.org Git - postgresql/commit
Add a few comments about ANALYZE's strategy for collecting MCVs.
authorTom Lane <tgl@sss.pgh.pa.us>
Mon, 4 Apr 2016 21:06:33 +0000 (17:06 -0400)
committerTom Lane <tgl@sss.pgh.pa.us>
Mon, 4 Apr 2016 21:06:33 +0000 (17:06 -0400)
commit3c69b33f459f62fe6db66c386ef12620ea697f74
tree26c427977d1af2e1c64b62c774376fb8d33b08aa
parent391159e03a8b69dd04a1432ceb800c7c4c3d608c
Add a few comments about ANALYZE's strategy for collecting MCVs.

Alex Shulgin complained that the underlying strategy wasn't all that
apparent, particularly not the fact that we intentionally have two
code paths depending on whether we think the column has a limited set
of possible values or not.  Try to make it clearer.
src/backend/commands/analyze.c