refer to an attachment to this jira for a list of GUCs that are identified in src/backend/utils/misc/guc.c as members of the DEVELOPER_OPTIONS config group. there is some inconsistency with respect to documenting GUCs of this type and/or whether or not the GUC shows up in hawq config output.
from Ruilong Huo via hawq dev mailing list: "DEVELOPER GUC: should not in doc; should not show in hawq config"
1. identify if each GUC in the list is correctly classified as a developer option
2. for each GUC identified as a "real" developer option, ensure that the GUC_NO_SHOW_ALL flag is set in the GUC table in guc.c
3. for each GUC identified as a "real" developer option, identify how to deal with those that are currently documented