Thread: pg_restore speed

pg_restore speed

From
Colton A Smith
Date:
Hi:

   I have a 90G postgis-enabled postgresql
database that I'm upgrading from 8.1.5 to
8.2.1.  I initiated pg_restore nearly
six days ago and it's still churning away,
surely but slowly.  Is this amount of
time normal? Or have I done something
wrong?

Any help is appreciated!

Thanks

Re: pg_restore speed

From
"Joshua D. Drake"
Date:
Colton A Smith wrote:
> Hi:
>
>   I have a 90G postgis-enabled postgresql
> database that I'm upgrading from 8.1.5 to
> 8.2.1.  I initiated pg_restore nearly
> six days ago and it's still churning away,
> surely but slowly.  Is this amount of
> time normal? Or have I done something
> wrong?

6 days seems like an awful long time I could see 12-15 hours. What type
of machine do you have? What was the pg_dump command you used and
respective pg_restore?

>
> Any help is appreciated!
>
> Thanks
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
>       subscribe-nomail command to majordomo@postgresql.org so that your
>       message can get through to the mailing list cleanly
>


--

      === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997
             http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/


Re: pg_restore speed

From
Tom Lane
Date:
"Joshua D. Drake" <jd@commandprompt.com> writes:
> Colton A Smith wrote:
>> I have a 90G postgis-enabled postgresql
>> database that I'm upgrading from 8.1.5 to
>> 8.2.1.  I initiated pg_restore nearly
>> six days ago and it's still churning away,
>> surely but slowly.  Is this amount of
>> time normal? Or have I done something
>> wrong?

> 6 days seems like an awful long time I could see 12-15 hours. What type
> of machine do you have? What was the pg_dump command you used and
> respective pg_restore?

What is the restore actually doing at the moment?  (Look in
pg_stat_activity)

For such a large DB I'd think you'd really need to increase
shared_buffers, checkpoint_segments, and maintenance_work_mem well
beyond their default values ... did you do that before starting to
restore?  (Actually I think you could probably do the latter two
on-the-fly without disturbing the restore, so that might be something
to try before giving up and starting over.)

            regards, tom lane