Hurrah !
End of a long story !
I should have read the messages from the backup dialog more carefully, and I would have seen the pg_dump command !
And I would have noticed that PG Admin uses its own pg_dump.
So my problems (using pg_dump v8.2 instead of PG Admin: SERIAL replaced by INT and SEQUENCES, and going from v1.6.1 to
v1.6.2:wrong UTF-8 format) can be solved just by using a previous version of pg_dump (the one from PGAdmin 1.4., for
example)to generate my file.
Sorry for being a pain.
And thanks for solving that problem in the end.
Saying that, as Guillaume suggested, it could be a good idea to be able to choose the pg_dump, one wants to use with PG
Admin... but I suppose replacing the pg_dump.exe file in the PG Admin directory should do the trick.
Cheers,
L@u
The Computing Froggy
----- Message d'origine ----
De : Dave Page <dpage@postgresql.org>
À : Laurent ROCHE <laurent_roche@yahoo.com>
Cc : pgadmin-support@postgresql.org
Envoyé le : Mercredi, 10 Janvier 2007, 10h56mn 47s
Objet : Re: Re : Re : [pgadmin-support] Backup file not UTF-8 (introduced bug
Laurent ROCHE wrote:
> Hi,
>
> But the problem is that using pg_dump does not produce the same file format than PG Admin (re: SERIAL, see on of my
previouspost). So you are using the pg_dump routine when I use the command line: it's different anyway with different
options.
>
How can it not produce the same file format - it calls pg_dump to do the
backup!!
As for the options, pgAdmin shows the command line it uses on the
messages tab when you run the backup so you can easily duplicate what
it's doing.
Regards, Dave
__________________________________________________
Do You Yahoo!?
En finir avec le spam? Yahoo! Mail vous offre la meilleure protection possible contre les messages non sollicités
http://mail.yahoo.fr Yahoo! Mail