Hi Martijn,
Thank you very much for reply. It has worked perfectly.
Have a good life,
All beings be happy
Martijn van Oosterhout escribió:
On Tue, May 13, 2008 at 05:37:27PM +0200, J. Manuel Velasco - UBILIBET wrote:
I have the idea to create the database and the role and then
On Tue, May 13, 2008 at 05:37:27PM +0200, J. Manuel Velasco - UBILIBET wrote:
> I have the idea to create the database and the role and then load the
> pg_dump result from the other database. The old databse has encoding
> LATIN2 so I try to create with this encoding and I get the message(*):
> E
Hello,
Thanks for your quick replay, but I had other thing to do and I haven't
could check your hint before.
I started a new postgresql-8-3 installation. Set it up, ok
I have the idea to create the database and the role and then load the
pg_dump result from the other database. The old databs
On Tue, May 13, 2008 at 09:00:49AM +0200, J. Manuel Velasco - UBILIBET wrote:
> Hello,
>
> I have installed a new postgresql server and I need to recover an old
> database on it.
> The database I have to recover has LATIN2 as encoding and when i try to
> restore it into the new one I get error m
Hello,
there is no possibility change encoding after database is created. You
can only change dynamic encoding for clients,
example: czech environment use cp1250 for win clients and latin2 for
others clients generally. I init in initdb databse for latin2 encoding. If
some people goes from lati
