aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeCustom.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2017-06-04 13:34:05 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2017-06-04 13:34:05 -0400
commit9db7d47f909482ac2b76c28f5e9a2ef48fb19b9d (patch)
treee940c41990ca01f73d28f234d283190c6a5fa364 /src/backend/executor/nodeCustom.c
parent0d1885266630eee1de5c43af463fe2b921451932 (diff)
downloadpostgresql-9db7d47f909482ac2b76c28f5e9a2ef48fb19b9d.tar.gz
postgresql-9db7d47f909482ac2b76c28f5e9a2ef48fb19b9d.zip
#ifdef out assorted unused GEQO code.
I'd always assumed that backend/optimizer/geqo/'s remarkably poor showing on code coverage metrics was because we weren't exercising it much in the regression tests. But it turns out that a good chunk of the problem is that there's a bunch of code that is physically unreachable (because the calls to it are #ifdef'd out in geqo_main.c) but is being built anyway. Making the called code have #if guards similar to the calling code saves a couple of kilobytes of executable size and should make the coverage numbers more reflective of reality. It's arguable that we should just delete all the unused recombination mechanisms altogether, but I didn't feel a need to go that far today.
Diffstat (limited to 'src/backend/executor/nodeCustom.c')
0 files changed, 0 insertions, 0 deletions