> "Phillip Smith" <phillip.smith@weatherbeeta.com.au> writes:
> > I've been thinking about this, and while I don't agree it's a bug, I
> think
> > that perhaps PostgreSQL should raise a notice or warning that the
> > destination database has different encoding than the file being
> restored...?
>
> If Postgres actually *knows* that the encodings are different, it can
> deal with that. The cases that are problematic are where the software
> has been misinformed for one reason or another. I doubt that a warning
> issued (or not) on the basis of misinformation will be especially helpful.
How has the software been misinformed and how can we avoid it then? :)
The start of the pgdump sets the client encoding, so shouldn't that tell PG
that things could get strange?
THINK BEFORE YOU PRINT - Save paper if you don't really need to print this
*******************Confidentiality and Privilege Notice*******************
The material contained in this message is privileged and confidential to
the addressee. If you are not the addressee indicated in this message or
responsible for delivery of the message to such person, you may not copy
or deliver this message to anyone, and you should destroy it and kindly
notify the sender by reply email.
Information in this message that does not relate to the official business
of Weatherbeeta must be treated as neither given nor endorsed by Weatherbeeta.
Weatherbeeta, its employees, contractors or associates shall not be liable
for direct, indirect or consequential loss arising from transmission of this
message or any attachments
e-mail.
