| From: | "patrick keshishian" <pkeshish(at)gmail(dot)com> |
|---|---|
| To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: pg 7.4.x - pg_restore impossibly slow |
| Date: | 2006-04-14 07:10:57 |
| Message-ID: | 53b425b00604140010v718aa171p19d9253ce58d0006@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 4/13/06, Jim C. Nasby <jnasby(at)pervasive(dot)com> wrote:
> On Thu, Apr 13, 2006 at 06:26:00PM -0700, patrick keshishian wrote:
> > $ dropdb dbname
> > $ createdb dbname
> > $ pg_restore -vsOd dbname dbname.DUMP
>
> That step is pointless, because the next pg_restore will create the
> schema for you anyway.
Yes, I noticed this with the verbose output (random
non-standard option "-v").
I was providing all information (read: exact steps taken)
which may have been relevant to my post/question, so
that, I would avoid being guilty of omitting any possibly
significant, yet random information.
Thanks for the insight,
--patrick
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Francisco Reyes | 2006-04-14 11:30:25 | Re: Inserts optimization? |
| Previous Message | patrick keshishian | 2006-04-14 06:59:51 | Re: pg 7.4.x - pg_restore impossibly slow |