David Fetter <david@fetter.org> writes:
> When we have a bad default--and I'd argue that for anyone not
> developing PostgreSQL itself, showing system functions is a bad
> default--we should change it to something sane.
I disagree with your parenthetical argument here, mainly on the strength
of Greg's point about how that might hide the existence of conflicts.
But in any case the discussion here is first about what set of behaviors
we need to provide, and only second about which one should be default.
regards, tom lane
