[GENERAL] Differences in Unicode handling on Mac vs Linux?

2013-06-02 Thread Matt Daw
Howdy, I loaded a client's DB on my Mac to debug an unrelated bug, but I'm blocked because my Mac is rejecting SQL that works on our Linux production servers. Here's a simple case: # select * from shots where sg_poznÁmka is NULL; ERROR: column "sg_pozn�mka" does not exist LINE 1: select * from sh

Re: [GENERAL] Differences in Unicode handling on Mac vs Linux?

2013-06-02 Thread Tom Lane
Matt Daw writes: > Howdy, I loaded a client's DB on my Mac to debug an unrelated bug, but > I'm blocked because my Mac is rejecting SQL that works on our Linux > production servers. Here's a simple case: > # select * from shots where sg_poznÁmka is NULL; > ERROR: column "sg_pozn�mka" does not

Re: [GENERAL] Differences in Unicode handling on Mac vs Linux?

2013-06-02 Thread Matt Daw
> Hm ... what does "\d shots" say about the spelling of the column name? \d shots is the same on both systems: sg_poznÁmka | text | > OS X's Unicode locales are pretty crummy. I'm suspicious that there's > some sort of case-folding inconsistency h

Re: [GENERAL] Differences in Unicode handling on Mac vs Linux?

2013-06-02 Thread Ian Lawrence Barwick
2013/6/3 Tom Lane : > Matt Daw writes: >> Howdy, I loaded a client's DB on my Mac to debug an unrelated bug, but >> I'm blocked because my Mac is rejecting SQL that works on our Linux >> production servers. Here's a simple case: > >> # select * from shots where sg_poznÁmka is NULL; >> ERROR: colu