From: | Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com> |
---|---|
To: | Pavel Raiskup <praiskup(at)redhat(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_upgrade: make the locale comparison more tolerating |
Date: | 2014-01-24 09:24:49 |
Message-ID: | CAGPqQf1MiRr6=FgGY+kmuo3b4FpASXgRi7yKc6MncZ1hU4_j7g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello,
I started reviewing the patch. Go through the original mail thread to
understand
the need of fix and the actual problem.
http://www.postgresql.org/message-id/20121002155857.GE30089@momjian.us
Patch is using pg_valid_server_encoding() to compare the encoding which
looks
more correct. Did code walk through and it looks good to me. I tried to test
the patch on CentOS and its working fine. I am not quite knowledgeable
about other OS so on that perspective would good to have others view.
Here are the comment about the patch:
.) Patch gets cleanly apply on master ( using patch -p1 )
.) compilation done successful
.) Code walk through and logic looks good
.) Manual testing worked good for me
To test the issue I set the old database locale to en_US.utf8 and for new
database
locale to en_US.utf-8. WIth this when I tried pg_upgrade it failed with
"lc_collate cluster
values do not match: old "en_US.utf8", new "en_US.UTF-8". With the patch
pg_upgrade
running fine.
Regards,
From | Date | Subject | |
---|---|---|---|
Next Message | MauMau | 2014-01-24 10:36:52 | Re: [patch] Client-only installation on Windows |
Previous Message | Heikki Linnakangas | 2014-01-24 09:19:19 | Re: GIN improvements part 1: additional information |