From: | "Mag Gam" <magawake(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: best practices for dumping databases |
Date: | 2008-04-07 00:49:35 |
Message-ID: | 1cbd6f830804061749u6cd00778qba8c3ef1c3375712@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
On Sun, Apr 6, 2008 at 6:36 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Mag Gam" <magawake(at)gmail(dot)com> writes:
> > 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.
>
> Please provide details --- it should work anyway, in any remotely
> modern PG version.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-04-07 01:24:04 | Re: best practices for dumping databases |
Previous Message | Tom Lane | 2008-04-06 22:36:27 | Re: best practices for dumping databases |