From: | Herouth Maoz <herouth(at)oumail(dot)openu(dot)ac(dot)il> |
---|---|
To: | pgsql-general(at)postgreSQL(dot)org |
Subject: | Re: [GENERAL] pg-dump problem |
Date: | 1998-08-19 15:35:54 |
Message-ID: | l03110703b2009bfb82f2@[147.233.159.109] |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
At 17:51 +0300 on 19/8/98, Bruce Momjian wrote:
> I believe this was fixed in the coming 6.4 beta, September 1.
Ah, I see... now, where did I put that time machine... :)
Well, I thought I'd do a pg_dump -S and append the normal pg_dump to it.
Thus, the schema will be created twice, and whatever failed in the first
pass will work in the second.
The problem with that is that pg_dump -S dumps the indices, so the indices
will be created before the data copy - which will cause a great slow-down
upon restoration.
> I also believe we now show the load as it is being loaded by default.
> You can use a psql option to get that in earlier releases.
Which option? I used -e, but it doesn't echo the actual data, only the
queries themselves, so I had to guess that the line causing the display of
all slash commands was the "\." at the end of a copy operation.
Herouth
--
Herouth Maoz, Internet developer.
Open University of Israel - Telem project
http://telem.openu.ac.il/~herutma
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1998-08-19 16:42:07 | Re: [GENERAL] pg-dump problem |
Previous Message | Bruce Momjian | 1998-08-19 14:51:17 | Re: [GENERAL] pg-dump problem |