Re: best practices for dumping databases
| От | Mag Gam |
|---|---|
| Тема | Re: best practices for dumping databases |
| Дата | |
| Msg-id | 1cbd6f830804061749u6cd00778qba8c3ef1c3375712@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: best practices for dumping databases (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: best practices for dumping databases
|
| Список | pgsql-novice |
I am not able to reproduce this error now..strange!
I am running 8.3.0, and basically the error I was getting was "\m ignoring" when I tried to do a restore. I was using the redirect " psql foo < db.dump" and the "\i db.dump" method for the restore.
I will be vigilant and try to attempt this again if I find anything I will report it ASAP.
But, what is the correct practice to do db_dumps? pg_dump db should suffice?
Thanks
I am running 8.3.0, and basically the error I was getting was "\m ignoring" when I tried to do a restore. I was using the redirect " psql foo < db.dump" and the "\i db.dump" method for the restore.
I will be vigilant and try to attempt this again if I find anything I will report it ASAP.
But, what is the correct practice to do db_dumps? pg_dump db should suffice?
Thanks
On Sun, Apr 6, 2008 at 6:36 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
"Mag Gam" <magawake@gmail.com> writes:Please provide details --- it should work anyway, in any remotely
> What is the best way to dump a database?
> Currently, I am using pg_dump dbname. However, my data contains a lot of
> escape sequences and various characters which is causing a restore problem.
modern PG version.
regards, tom lane
В списке pgsql-novice по дате отправления: