| From: | Adam Dear <adear(at)usnx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Unable to dump database using pg_dump |
| Date: | 2008-06-12 16:33:14 |
| Message-ID: | 48514FCA.9020001@usnx.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Let me ask this question. Is there any other option for moving data
from one server to another that doesn't involve pg_dump? If I can get
the data out of this server, and onto my new one I don't care if the old
server gets fixed. I just need the data. The new server already has
the table structure, I just need the most current data to put into the
server.
Tom Lane wrote:
> Adam Dear <adear(at)usnx(dot)net> writes:
>> If I restored the data directory again wouldn't that undo the Vacuum
>> Freeze command that I did that has locked the database into the state
>> that it is in now?
>
> It'd undo the freeze, but that doesn't get you any closer to a solution.
> What you need is to get rid of the wrapped-around xmax in the (0,1)
> tuple.
>
> regards, tom lane
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adam Dear | 2008-06-12 16:53:46 | Re: Unable to dump database using pg_dump |
| Previous Message | Rowan | 2008-06-12 16:21:35 | understanding a nested query |