2014-09-03 16:01 GMT+02:00 Kevin Grittner <kgrittn@xxxxxxxxx>:
Pavel Stehule <pavel.stehule@xxxxxxxxx> wrote:
> 2014-09-03 15:25 GMT+02:00 Szymon Guz <mabewlun@xxxxxxxxx>:
>> I think we should have this in core, as this definitely is a bug.On a quick scan of the standard, it looks like our current behavior
>
> hard to say - anything about CHAR(N) is strange,
is non-conforming.
That is true, but since the only point of supporting CHAR(n) is to
> and this change can break existing applications :(
satisfy requirements of the standard, it might be something we
should do, if technically feasible.
It is true, but nobody reported bug yet, so who know, how this feature is used.
Probably it needs a deeper analyze of difference between Pg CHAR(n) and standard CHAR(n)
Pavel
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
