Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: BUG #2861: when backup UTF-8 database,pgdump add comments not encoded in UTF-8
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: "goodsforyou" <goodsforyou(at)gmail(dot)com>
- Cc: pgsql-bugs(at)postgresql(dot)org
- Subject: Re: BUG #2861: when backup UTF-8 database,pgdump add comments not encoded in UTF-8
- Date: Mon, 25 Dec 2006 15:46:39 -0500
"goodsforyou" <goodsforyou(at)gmail(dot)com> writes: > PostgreSQL version: 8.2.0 win32 > When I make a backup of a UTF8 database then pg_dump add some comment to > backup file: > -- Started on 2006-12-23 11:04:38 ä¸å½æ åæ¶é´ You *sure* that pg_dump is 8.2.0? Because we fixed that before 8.2 rc1 ... 2006-11-21 17:19 tgl * src/: backend/utils/error/elog.c, bin/pg_dump/pg_backup_archiver.c, bin/pg_dump/pg_dumpall.c: Suppress timezone (%Z) part of timestamp display when running on Windows, because on that platform strftime produces localized zone names in varying encodings. Even though it's only in a comment, this can cause encoding errors when reloading the dump script. Per suggestion from Andreas Seltenreich. Also, suppress %Z on Windows in the %s escape of log_line_prefix ... not sure why this one is different from the other two, but it shouldn't be. regards, tom lane
- References:
- Prev by Date: Re: SIMILAR TO incorrect with alternation
- Next by Date: Re: BUG #2857: Sequence and table partitioning
- Previous by thread: BUG #2861: when backup UTF-8 database,pgdump add comments not encoded in UTF-8
- Next by thread: BUG #2862: ERROR: failed to build any 7-way joins
- Indexes: