Tom Lane wrote:
> Aside from the reality that apps aren't very consistent about their
> quoting behavior, the fly in this ointment is that whenever you query
> the database catalogs you will see the stored spelling of the name.
> So apps that rely on seeing the same spelling in the catalog that they
> entered could break. (In practice this doesn't seem to be as big a
> problem as the sloppy-quoting-behavior issue, though.)
Shouldn't apps only really be querying the information schema if they're
expecting spec compliant behavior? If so, a GUC variable with an access
function ought to be enough to get up or down casing as desired, I'd think.
Joe