From: | Matt Starr <mstarr(at)logicworks(dot)net> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Unsubscribe |
Date: | 2007-08-02 03:32:30 |
Message-ID: | 1AF2A598DDC1BF4EBDDF8DF87A823D17019AD5ABEC@exchange3.corp.logicworks.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
________________________________________
From: pgsql-general-owner(at)postgresql(dot)org [pgsql-general-owner(at)postgresql(dot)org] On Behalf Of Merlin Moncure [mmoncure(at)gmail(dot)com]
Sent: Wednesday, August 01, 2007 11:14 PM
To: barry(dot)c(dot)dowell(dot)1(at)gsfc(dot)nasa(dot)gov
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] Move database from Solaris to Windows
On 8/2/07, Barry C Dowell <barry(dot)c(dot)dowell(dot)1(at)gsfc(dot)nasa(dot)gov> wrote:
> Ok, if you can forgive the possible stupid answer and help pull me a long a
> bit more, in answer to this:
>
> >> Yes, dump/restore is pretty much the standard to move dbs across
> architectures so we'll need more to work with. One thing to check, did you
> make sure that your dump was in the same encoding as the database you
> created on your Windows server?
>
> How do I know what encoding was used on one database (on one OS) versus the
> other?
psql -l
lists the encoding. postgresql on windows iirc defaults to sql_ascii
which is actually the most forgiving but not a great choice. linux
defaults to utf-8.
can you post the exact text of the error?
merlin
---------------------------(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
From | Date | Subject | |
---|---|---|---|
Next Message | Andrej Ricnik-Bay | 2007-08-02 03:56:44 | Re: Linux distro |
Previous Message | Merlin Moncure | 2007-08-02 03:14:35 | Re: Move database from Solaris to Windows |