![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
When I pg_dump -c trouble > trouble_dump, take the file down and cat trouble_dump | psql trouble it shows as LATIN1 in the local listing. Then I dump it again locally, upload and cat, it shows as SQL_ASCII. |
#3
| |||
| |||
|
|
Aarni =?iso-8859-1?q?Ruuhim=E4ki?= <aarni.ruuhimaki (AT) kymi (DOT) com> writes: When I pg_dump -c trouble > trouble_dump, take the file down and cat trouble_dump | psql trouble it shows as LATIN1 in the local listing. Then I dump it again locally, upload and cat, it shows as SQL_ASCII. I believe the default encoding for a newly-created database is the same encoding as template1 --- since the two installations were initdb'd with different default encodings, the behavior you're describing is not too surprising. You can specify the encoding to use when you create a database, though. BTW, 7.3.3 has a serious known bug in the restart logic ... you ought to update to 7.3.4 or 7.3.5 before you get bitten. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings |
![]() |
| Thread Tools | |
| Display Modes | |
| |