Re: client_encoding issue with SQL_ASCII on 8.3 to 10 upgrade

On Mon, Apr 16, 2018 at 2:26 PM, Adrian Klaver wrote: > On 04/16/2018 10:18 AM, Keith Fiske wrote: > >> >> >> On Mon, Apr 16, 2018 at 12:21 PM, Tom Lane > t...@sss.pgh.pa.us>> wrote: >> >> > >> So playing around with the "client_encoding" configuration option in >> postgresql.conf. According to t

Re: client_encoding issue with SQL_ASCII on 8.3 to 10 upgrade

On 04/16/2018 10:18 AM, Keith Fiske wrote: On Mon, Apr 16, 2018 at 12:21 PM, Tom Lane > wrote: So playing around with the "client_encoding" configuration option in postgresql.conf. According to the docs, setting this should set the default encoding for any cli

Re: client_encoding issue with SQL_ASCII on 8.3 to 10 upgrade

On 04/16/2018 10:18 AM, Keith Fiske wrote: So playing around with the "client_encoding" configuration option in postgresql.conf. According to the docs, setting this should set the default encoding for any client that connects, right? https://www.postgresql.org/docs/10/static/runtime-con

Re: client_encoding issue with SQL_ASCII on 8.3 to 10 upgrade

On 04/16/2018 10:18 AM, Keith Fiske wrote: So playing around with the "client_encoding" configuration option in postgresql.conf. According to the docs, setting this should set the default encoding for any client that connects, right? For any client that does not set a client_encoding when

Re: client_encoding issue with SQL_ASCII on 8.3 to 10 upgrade

On Mon, Apr 16, 2018 at 12:21 PM, Tom Lane wrote: > Keith Fiske writes: > > On Mon, Apr 16, 2018 at 12:09 PM, Tom Lane wrote: > >> This is not a great idea, no. You could be getting strange misbehaviors > >> in e.g. string comparison, because strcoll() will expect UTF8 data and > >> will likel

Re: client_encoding issue with SQL_ASCII on 8.3 to 10 upgrade

On Mon, Apr 16, 2018 at 12:30 PM, Vick Khera wrote: > Hi Keith, > > Not sure if this will help but a couple of years ago I migrated from an > SQL_ASCII encoding to UTF8. The data was primarily ASCII with some windows > garbage, and a little bit of UTF8 from customers filling out forms that > were

Re: client_encoding issue with SQL_ASCII on 8.3 to 10 upgrade

On Mon, Apr 16, 2018 at 12:21 PM, Tom Lane wrote: > Keith Fiske writes: > > On Mon, Apr 16, 2018 at 12:09 PM, Tom Lane wrote: > >> This is not a great idea, no. You could be getting strange misbehaviors > >> in e.g. string comparison, because strcoll() will expect UTF8 data and > >> will likel

Re: client_encoding issue with SQL_ASCII on 8.3 to 10 upgrade

Hi Keith, Not sure if this will help but a couple of years ago I migrated from an SQL_ASCII encoding to UTF8. The data was primarily ASCII with some windows garbage, and a little bit of UTF8 from customers filling out forms that were not specifically encoded anything. I wrote a utility that in-pl

Re: client_encoding issue with SQL_ASCII on 8.3 to 10 upgrade

Keith Fiske writes: > On Mon, Apr 16, 2018 at 12:09 PM, Tom Lane wrote: >> This is not a great idea, no. You could be getting strange misbehaviors >> in e.g. string comparison, because strcoll() will expect UTF8 data and >> will likely not cope well with data that isn't valid in that encoding.

Re: client_encoding issue with SQL_ASCII on 8.3 to 10 upgrade

On Mon, Apr 16, 2018 at 12:09 PM, Tom Lane wrote: > Keith Fiske writes: > > Running into an issue with helping a client upgrade from 8.3 to 10 (yes, > I > > know, please keep the out of support comments to a minimum, thanks :). > > > The old database was in SQL_ASCII and it needs to stay that wa

Re: client_encoding issue with SQL_ASCII on 8.3 to 10 upgrade

Keith Fiske writes: > Running into an issue with helping a client upgrade from 8.3 to 10 (yes, I > know, please keep the out of support comments to a minimum, thanks :). > The old database was in SQL_ASCII and it needs to stay that way for now > unfortunately. The dump and restore itself works fi

Re: client_encoding issue with SQL_ASCII on 8.3 to 10 upgrade

On 04/16/2018 08:16 AM, Keith Fiske wrote: Running into an issue with helping a client upgrade from 8.3 to 10 (yes, I know, please keep the out of support comments to a minimum, thanks :). The old database was in SQL_ASCII and it needs to stay that way for now unfortunately. The dump and resto

Re: client_encoding issue with SQL_ASCII on 8.3 to 10 upgrade

On 04/16/2018 08:16 AM, Keith Fiske wrote: Running into an issue with helping a client upgrade from 8.3 to 10 (yes, I know, please keep the out of support comments to a minimum, thanks :). The old database was in SQL_ASCII and it needs to stay that way for now unfortunately. The dump and resto