nutes to the PostgreSQL
value is one way but that seems kind of dangerous without
understanding what's really going on here.
If any light is shed on this I would be greatly appreciative.
Regards,
Preston Landers
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Fri, Sep 9, 2011 at 5:13 PM, Tom Lane wrote:
>> Yet PostgreSQL
>> shows a value that is exactly 26 minutes behind the others (12:09:40).
>
> You've fat-fingered the to_char usage --- MM is month, not minutes
> (I think you want MI for that).
>
Yep, that's exactly it. Thanks so much for your h
252 for
now.
If the postgresql encoding "WIN" really is intended to be Western
codepage 1252, then the docs (and possibly the code?) obviously need to
be fixed, then a separate Cyrillic WIN1251 encoding created.
thanks,
Preston Landers
(pibble @t yahoo dot com)
---(
Peter Eisentraut wrote:
>Am Samstag, 12. Februar 2005 23:32 schrieb Preston Landers:
>> If the postgresql encoding "WIN" is intended to be Cyrillic 1251,
then
>> it should be labeled as such in the docs to avoid confusion.
>Well, isn't it? You pointed to the pl
