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. > > hard to say - anything about CHAR(N) is strange, On a quick scan of the standard, it looks like our current behavior is non-conforming. > and this change can break existing applications :( That is true, but since the only point of supporting CHAR(n) is to satisfy requirements of the standard, it might be something we should do, if technically feasible. -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
