Re: [GENERAL] pg-dump problem

> 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.

Yep. All the index creation is at the end, so you can just delete them.

>
> > 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.

Oh, you want to see the data? I think the new version does this. Not sure.

--
Bruce Momjian | 830 Blythe Avenue
maillist(at)candle(dot)pha(dot)pa(dot)us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)