Wolf Rogner [2008-01-23 19:38 -0000]:
> I get the feeling that you prefer spending time discussing instead
> of fixing.
No, I don't. I spent a hell of a lot of time to make the locale
handling in Postgresql work right. Without working locales, collation
and string comparisons will fail, and the client libs will return
strings which have an invalid encoding. I am not going to deliberately
break postgresql to create DB instances which have nonobvious bugs in
it.
That's FUD. We live in a free world, so I won't stop you from doing
whatever blogs you want, or configuring your local psql installation
however you want. If you don't need non-ASCII characters, that's fine.
But don't insist that the PostgreSQL packages are broken without even
listening to my explanation. Your system is broken (it sets LANG and
LC_* to invalid values), the PostgreSQL packages clearly tell you
about the condition. If you ignore it, that's fine. Calling it a bug
is not justified.
Wolf Rogner [2008-01-23 19:38 -0000]:
> I get the feeling that you prefer spending time discussing instead
> of fixing.
No, I don't. I spent a hell of a lot of time to make the locale
handling in Postgresql work right. Without working locales, collation
and string comparisons will fail, and the client libs will return
strings which have an invalid encoding. I am not going to deliberately
break postgresql to create DB instances which have nonobvious bugs in
it.
http:// www.postgresql. org/docs/ 8.2/interactive /locale. html www.postgresql. org/docs/ 8.2/interactive /multibyte. html
http://
> Read my blog on this: wolfs-ubuntu. blogspot. com/2007/ 11/installing- postgresql- 82-on-710- server. html
> http://
That's FUD. We live in a free world, so I won't stop you from doing
whatever blogs you want, or configuring your local psql installation
however you want. If you don't need non-ASCII characters, that's fine.
But don't insist that the PostgreSQL packages are broken without even
listening to my explanation. Your system is broken (it sets LANG and
LC_* to invalid values), the PostgreSQL packages clearly tell you
about the condition. If you ignore it, that's fine. Calling it a bug
is not justified.