Re: information_schema.columns changes needed for OLEDB

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org, Konstantin Izmailov <kizmailov(at)gmail(dot)com>
Subject: Re: information_schema.columns changes needed for OLEDB
Date: 2009-07-06 19:16:12
Message-ID: 19888.1246907772@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2009-07-06 19:37:16 Maintenance Policy?
Previous Message Peter Eisentraut 2009-07-06 18:37:52 Re: information_schema.columns changes needed for OLEDB