Re: problem with pg_restore? - Mailing list pgsql-general

From Jasen Betts
Subject Re: problem with pg_restore?
Date
Msg-id h49f4c$43n$1@reversiblemaps.ath.cx
Whole thread Raw
In response to problem with pg_restore?  (Jim Michaels <jmichae3@yahoo.com>)
Responses Re: problem with pg_restore?
List pgsql-general
On 2009-07-14, Jim Michaels <jmichae3@yahoo.com> wrote:
>
> --0-1060148048-1247615236=:84835
> Content-Type: text/plain; charset=us-ascii
>
> I am having problems with pg_restore.  pg_restore --file=c:\pg-jmichae3-7-13-2009.sql --verbose --host=localhost
--port=5432--username=postgres 
>
> this just hangs.
> I am restoring from 8.3.7 to 8.4 - what did I do wrong?


> could somebody rewrite pg_dumpall and pg_dump so that it makes editable dumps?
> most programmer's text editors can't handle more than 2000 characters per line.

any text editor with a line length limit shorter than 1 megabyte is a
liability.  that said if you dump as inserts there's probably a way to
use sed to split the long strings and still have a loadable dump.

> and I want to be able to edit my dumps.

I find that jed is powerful, fast, and reasonably easy to use. and had
no problem with 2.3MB lines.

gnome-text-editor ("gedit") handles lines of tens of thousands of
characters OK but seems to have problems displaying million character
lines,

I expect ther big guns "vim" and "emacs" also have no problems with
long lines.


pgsql-general by date:

Previous
From: "Albe Laurenz"
Date:
Subject: Re: enabling join_collapse_limit for a single query only
Next
From: Jasen Betts
Date:
Subject: Re: Server Backup: pg_dump vs pg_dumpall