El dÃa 23 de marzo de 2011 11:18, Adrian Klaver <adrian.klaver@xxxxxxxxx> escribiÃ: > On Wednesday, March 23, 2011 6:57:35 am MartÃn MarquÃs wrote: > >> Now I'm getting weirder things. I did a pg_dump with -d option and the > >> dump adds strange caracters: > > As previously stated try using the 8.4 version of pg_dump to dump the 8.3 > database. FYI in 8.4+ there is no -d option anymore, it has become --inserts > to reduce confusion with other commands where -d specified the database. Ok, did a remote dump (from the development server which has pg 8.4) and I got a similar error: psql:siprebi-bu.sql:27374: ERROR: sintaxis de entrada no v<C3><A1>lida para tipo bytea CONTEXT: COPY novedades_fotos, l<C3><AD>nea 273, columna foto: <C2><AB>\377\330\377\340\000\020JFIF\000\001\001\001\000`\000`\000\000\377\341<\310Exif\000\000II *\000\010\0...<C2><BB> psql:siprebi-bu.sql:3477848: ERROR: la sintaxis de entrada no es v<C3><A1>lida para integer: <C2><AB>q43116<C2><BB> CONTEXT: COPY objetos, l<C3><AD>nea 99185, columna codigo: <C2><AB>q43116<C2><BB> > >> > Also make sure your 8.3 installation doesn't have a non-default bytea > >> > encoding setting (not sure when that setting was introduced, so there > >> > may not even be such a setting). > >> > >> bytea has encoding? I thought it was plain binary data. > > I think he was talking about bytea_output, which appeared in 9.0. > > In any event you may want to verify that the encodings/locales for the two > databases are the same. > All configurations have UTF-8 -- MartÃn MarquÃs select 'martin.marques' || '@' || 'gmail.com' DBA, Programador, Administrador -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
