Re: [pgadmin-support] "Invalid byte sequence" message

2011-02-23 Thread Guillaume Lelarge
Le 23/02/2011 23:57, Vik Reykja a écrit : > On Wed, Feb 23, 2011 at 23:37, Guillaume Lelarge > wrote: > >> >> >>> >>> I disagree. Any system that offers to write my messages in French should >> do >>> so correctly, *especially* if it's the default. >>> >> Any production server should have

Re: [pgadmin-support] "Invalid byte sequence" message

2011-02-23 Thread Vik Reykja
On Wed, Feb 23, 2011 at 23:37, Guillaume Lelarge wrote: > >> > > > > I disagree. Any system that offers to write my messages in French should > do > > so correctly, *especially* if it's the default. > > > > >> Any production server should have lc_messages set to C. > Yeah. There are three main i

Re: [pgadmin-support] "Invalid byte sequence" message

2011-02-23 Thread Guillaume Lelarge
Le 23/02/2011 23:20, Vik Reykja a écrit : > On Wed, Feb 23, 2011 at 23:11, Guillaume Lelarge > wrote: > >> > default) on a French Windows. >>> >>> See this unresolved thread for more info: >>> http://archives.postgresql.org/pgsql-bugs/2010-09/msg00138.php >>> >> >>> I get it quite easily with LC

Re: [pgadmin-support] "Invalid byte sequence" message

2011-02-23 Thread Vik Reykja
On Wed, Feb 23, 2011 at 23:11, Guillaume Lelarge wrote: > > default) on a French Windows. > > > > See this unresolved thread for more info: > > http://archives.postgresql.org/pgsql-bugs/2010-09/msg00138.php > > > > > I get it quite easily with LC_MESSAGES = 'French, France' (the > installer's > T

Re: [pgadmin-support] "Invalid byte sequence" message

2011-02-23 Thread Guillaume Lelarge
Le 23/02/2011 22:51, Vik Reykja a écrit : > On Wed, Feb 23, 2011 at 21:41, Guillaume Lelarge > wrote: > >> Le 22/02/2011 21:58, Guillaume Lelarge a écrit : >>> Le 16/02/2011 14:21, Maximilian Tyrtania a écrit : Just found this in my log file: ERROR: invalid byte sequence for >> en

Re: [pgadmin-support] "Invalid byte sequence" message

2011-02-23 Thread Vik Reykja
On Wed, Feb 23, 2011 at 21:41, Guillaume Lelarge wrote: > Le 22/02/2011 21:58, Guillaume Lelarge a écrit : > > Le 16/02/2011 14:21, Maximilian Tyrtania a écrit : > >> Just found this in my log file: > >> > >> ERROR: invalid byte sequence for > encoding "UTF8": 0xe3bc64 > >> STATEMENT: SELECT > p

Re: [pgadmin-support] "Invalid byte sequence" message

2011-02-23 Thread Little, Douglas
We see this a lot with web applications where users cut/paste from MS-Word. In our case, the web app and db (oracle) are the same character set, so no translation or validation is done. Oracle will store the values, even though they aren't valid UTF8 characters. We run into problems when the v

Re: [pgadmin-support] dynamic results of a PG_Dump or pg_Restore in the list

2011-02-23 Thread Guillaume Lelarge
Le 17/02/2011 00:08, Doug Easterbrook a écrit : > hi Guillaume: > > I hope screenshots are ok to the list to explain what I mean. If you are > running a SQL 'Vacuum Verbose' and watch the messages on the 'message' > window, they scroll as postgres does its thing. > > I mispoke a little, but t

Re: [pgadmin-support] Bug -PGAdmin 1.12.2

2011-02-23 Thread Guillaume Lelarge
Le 22/02/2011 23:37, Melvin Davidson a écrit : >> Works for me here. What are your exact steps? >> >> Steps to duplicate: >> >> 1. Right Click on a database >> 2. Click on Backup >> 3. In popup screen, specify filename. >> 4. Click the Objects Tab >> 5. Uncheck the database (1st box) >> 6. Specific

Re: [pgadmin-support] Bug report: Syntax Coloring

2011-02-23 Thread Guillaume Lelarge
Le 23/02/2011 00:10, Peter Geoghegan a écrit : > On 22 February 2011 20:56, Guillaume Lelarge wrote: > >> You're right. I added a ticket to work on this later. > > I've noticed in the past that syntax highlighting is a bit broken. > It's possible to break it by copying and pasting. Perhaps I'll

Re: [pgadmin-support] "Invalid byte sequence" message

2011-02-23 Thread Guillaume Lelarge
Le 22/02/2011 21:58, Guillaume Lelarge a écrit : > Le 16/02/2011 14:21, Maximilian Tyrtania a écrit : >> Just found this in my log file: >> >> ERROR: invalid byte sequence for >> encoding "UTF8": 0xe3bc64 >> STATEMENT: SELECT >> pg_file_read('pg_log/postgresql-2011-02-16_00.log', 10, 50