pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
pg_restore speed
3+ messages / 3 participants
[nested] [flat]

* pg_restore speed
@ 2007-01-18 15:28  Colton A Smith <smith@cs.utk.edu>
  0 siblings, 1 reply; 3+ messages in thread

From: Colton A Smith @ 2007-01-18 15:28 UTC (permalink / raw)
  To: pgsql-admin

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



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: pg_restore speed
@ 2007-01-24 22:49  Joshua D. Drake <jd@commandprompt.com>
  parent: Colton A Smith <smith@cs.utk.edu>
  0 siblings, 1 reply; 3+ messages in thread

From: Joshua D. Drake @ 2007-01-24 22:49 UTC (permalink / raw)
  To: Colton A Smith <smith@cs.utk.edu>; +Cc: pgsql-admin

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/




^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: pg_restore speed
@ 2007-01-25 00:24  Tom Lane <tgl@sss.pgh.pa.us>
  parent: Joshua D. Drake <jd@commandprompt.com>
  0 siblings, 0 replies; 3+ messages in thread

From: Tom Lane @ 2007-01-25 00:24 UTC (permalink / raw)
  To: Joshua D. Drake <jd@commandprompt.com>; +Cc: Colton A Smith <smith@cs.utk.edu>; pgsql-admin

"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



^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2007-01-25 00:24 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2007-01-18 15:28 pg_restore speed Colton A Smith <smith@cs.utk.edu>
2007-01-24 22:49 ` Joshua D. Drake <jd@commandprompt.com>
2007-01-25 00:24   ` Tom Lane <tgl@sss.pgh.pa.us>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox