Shouldn't pg_settings.enumvals be array of text?

Currently, pg_settings.enumvals presents a list of strings formatted in
an ad-hoc manner. Shouldn't we be presenting this as text[], so that
clients don't need special-purpose code to break it apart?

Another possible argument is that the values ought to be separated by
newlines instead of ", ", which would still be a special-purpose format
but it would probably look better in modern psql versions. At least it
wouldn't be contributing to the problem of the view's output being
ridiculously wide.

Comments?

regards, tom lane