In trying to walk through (trace) code execution paths, I see that PELOTONFILE is not always correct. I've seen this before too, but previously thought it was my error.
With FILE the filename is correct.
2018-04-17 15:49:50 [/home/pakhtar/proj/pa_index_scan/peloton/src/include/plann\
er/seq_scan_plan.h:45:SeqScanPlan] DEBUG - Enter SeqScanPlan
With PELOTONFILE the filename is definitely not right.
2018-04-17 16:08:42 [/home/proj/pa_index_scan/peloton/src/optimizer/stats/tuple\
_samples_storage.cpp:45:SeqScanPlan] DEBUG - Enter SeqScanPlan
In trying to walk through (trace) code execution paths, I see that PELOTONFILE is not always correct. I've seen this before too, but previously thought it was my error.
With FILE the filename is correct. 2018-04-17 15:49:50 [/home/pakhtar/proj/pa_index_scan/peloton/src/include/plann\ er/seq_scan_plan.h:45:SeqScanPlan] DEBUG - Enter SeqScanPlan
With PELOTONFILE the filename is definitely not right. 2018-04-17 16:08:42 [/home/proj/pa_index_scan/peloton/src/optimizer/stats/tuple\ _samples_storage.cpp:45:SeqScanPlan] DEBUG - Enter SeqScanPlan