Re: [GENERAL] encodings
No, I didn't, I'm just courious. Regards, Zlatko - Original Message - From: Michael Fuhr [EMAIL PROTECTED] To: Zlatko Matić [EMAIL PROTECTED] Cc: pgsql-general@postgresql.org Sent: Sunday, July 22, 2007 5:41 AM Subject: Re: [GENERAL] encodings On Sat, Jul 21, 2007 at 10:24:38PM +0200, Zlatko Matić wrote: If I have an UTF8 database, dump it and the restore as WIN1250 database, then dump it again and restore as UTF8, would structure of the database (schema) be exactly the same as initial database, or something will change in the process? In other words, does encoding influence only data stored in tables, or it influences database structure as well? I can't think of how the encoding would influence the structure. Are you seeing behavior that suggests otherwise? -- Michael Fuhr ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org/
[GENERAL] encodings
Hello. If I have an UTF8 database, dump it and the restore as WIN1250 database, then dump it again and restore as UTF8, would structure of the database (schema) be exactly the same as initial database, or something will change in the process? In other words, does encoding influence only data stored in tables, or it influences database structure as well? Thanks. Zlatko
Re: [GENERAL] encodings
On Sat, Jul 21, 2007 at 10:24:38PM +0200, Zlatko Matić wrote: If I have an UTF8 database, dump it and the restore as WIN1250 database, then dump it again and restore as UTF8, would structure of the database (schema) be exactly the same as initial database, or something will change in the process? In other words, does encoding influence only data stored in tables, or it influences database structure as well? I can't think of how the encoding would influence the structure. Are you seeing behavior that suggests otherwise? -- Michael Fuhr ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [GENERAL] Encodings
Am Montag, 20. Februar 2006 08:55 schrieb Jan Cruz: When restoring a dump from sql_ascii encoding to latin9/utf8 This statement is both poorly specified and nonsensical. Please give us a more precise account of what you are doing. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[GENERAL] Encodings
When restoring a dump from sql_ascii encoding to latin9/utf8 the THIS STRING| result to THIS STRINGŠ thus it aborted the restore. When I tried to dump a latin9/utf8 and restore it with the same encoding having same string it goes well but it took a very long time to copy all data. (1.6gb dump for 24/hrs) So far I don't know what seems to be the problem why it took so long to copy the dump if it is already in latin9/utf8 encoding to latin9/utf8 database.
