Re: pg_dump native format will not restore correctly

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Scot Kreienkamp" <SKreien(at)la-z-boy(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: pg_dump native format will not restore correctly
Date: 2009-11-05 15:53:11
Message-ID: 21304.1257436391@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Scot Kreienkamp" <SKreien(at)la-z-boy(dot)com> writes:
> Another strange thing I just found when composing this email... If I set
> limit 5 on the query it works on the soldtrx table, but if I don't set a
> limit it just hangs.

Is it chewing CPU, chewing I/O, or just sitting? If the latter, try
attaching to the backend with gdb and getting a stack trace.

I'm still not buying the theory that the dump/restore method has
something to do with it. You might try the test yourself: run
pg_restore's output into a text file and compare with the text dump.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Scot Kreienkamp 2009-11-05 15:59:52 Re: pg_dump native format will not restore correctly
Previous Message cholid 2009-11-05 15:50:13 Database connection error, try to reset the connection parameters