Re: saving a view with pg_dump

--Howdy

--I'm looking at the page for restoration and I'm having a few
problems.

--In the docs, it suggest that I do the cat file* | psql database,
but I get other errors with using the cat command

[snip error]
bash: /bin/cat: Argument list too long

[/snip error]

--I'm trying to do something like `ls -1` files* | psql database
and I'm not getting any successful messages.

--I got a few other errors ... I supposed I was thinking
that the system files from before would be save and I wouldn't
have to create those by hand (users, groups, etc).

--I know this seems silly, but, why can't I copy the original
files back to the database directory after I've upgraded
postgres? doesn't that give you most of the same things
(OID, system files, users, etc ... )?

--Just curious ...

-X

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Friday, August 02, 2002 8:16 PM
To: Johnson, Shaunn
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] saving a view with pg_dump

"Johnson, Shaunn" <SJohnson6(at)bcbsm(dot)com> writes:
> sh: line 34: 13302 Broken pipe /backup/pg_dump -U postgres bcn
> 13303 File size limit exceeded| /bin/gzip >/backup/tools/bcndmp.gz

split is your friend. See
http://www.ca.postgresql.org/users-lounge/docs/7.2/postgres/backup.html#BACK
UP-DUMP-LARGE

regards, tom lane