[HACKERS] 8.3 to 8.4 Upgrade issues

We recently upgraded from 8.3 to 8.4 and have seen a performance degredation which we are trying to explain and I have been asked to get a second opinion on the cost of going from LATIN1 to UTF8 (Collation and CType) where the encoding remained SQL_ASCII.. Does anybody have experience on the

Re: [HACKERS] 8.3 to 8.4 Upgrade issues

Rod Taylor rod.tay...@gmail.com writes: Does anybody have experience on the cost, if any, of making this change? Pg 8.3: Encoding: SQL_ASCII LC_COLLATE: en_US LC_CTYPE: en_US Pg 8.4: Encoding: SQL_ASCII Collation: en_US.UTF-8 Ctype: en_US.UTF-8 Well, *both* of those settings

Re: [HACKERS] 8.3 to 8.4 Upgrade issues

On Tue, Aug 10, 2010 at 13:49, Tom Lane t...@sss.pgh.pa.us wrote: Rod Taylor rod.tay...@gmail.com writes: Does anybody have experience on the cost, if any, of making this change? Pg 8.3: Encoding: SQL_ASCII LC_COLLATE: en_US LC_CTYPE: en_US Pg 8.4: Encoding: SQL_ASCII Collation:

Re: [HACKERS] 8.3 to 8.4 Upgrade issues

Rod Taylor rod.tay...@gmail.com writes: Agreed with it being an interesting choice of settings. Nearly all of the data is 7-bit ASCII and what isn't seems to be a mix of UTF8, LATIN1, and LATIN15. I'm pretty sure it interpreted en_US to be LATIN1. There haven't been any noticeable changes in