Re: information_schema.columns changes needed for OLEDB - Mailing list pgsql-hackers

From Tom Lane
Subject Re: information_schema.columns changes needed for OLEDB
Date
Msg-id 19888.1246907772@sss.pgh.pa.us
Whole thread Raw
In response to Re: information_schema.columns changes needed for OLEDB  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: information_schema.columns changes needed for OLEDB  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> I have the attached patch that would make character_octet_length the product 
> of character_octet_length and the maximum octet length of a single character 
> in the selected server encoding.  So for UTF-8, this would be factor 4.  This
> doesn't exactly correspond to the behavior that you expect, but I think it's 
> more correct overall anyway.

+1, but that new query isn't very schema-safe ... I think it needs a few
"pg_catalog." qualifications.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: information_schema.columns changes needed for OLEDB
Next
From: "David E. Wheeler"
Date:
Subject: Maintenance Policy?