pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Frank Morton <fmorton@base2inc.com>
To: pgsql-sql@postgreSQL.org
Subject: Slow Inserts Leads To Unable To Dump
Date: Mon, 10 May 1999 08:17:05 -0500
Message-ID: <041c01be9ae7$668ea5a0$8355e5ce@base2inc.com> (raw)
References: <3736D569.F5A087E2@sinectis.com.ar>

Remember the thread last week about slow inserts? I still
have more to do, but basically I ended up waiting about 7
DAYS to insert 150,000 rows into a single table.

Now that that is done, I thought I should dump the database
before doing any more to save those 7 days if I mess up.
After processing 18 HOURS doing the "pg_dump -d", it ran
out of memory and quit. Are there tools to do this differently,
that is, not requiring the system to do a SELECT on the
whole table first? Just dump it? (I did try pg_dump without
-d but stopped it after an hour or so)

I am getting concerned that I can't really use postgreSQL
for large databases. Sure, some have built large databases,
but have any of you ever had to dump and restore them?
What happens when an update requires that? I think some
have reported 1,000,000 rows databases. By my calculation,
if you could get it to dump, it would take my database 46 DAYS
to reload if I get to that size. Maybe "copy" will help, but now
I'm more concerned about being totally unable to "dump."

I really like postgreSQL and think everyone working on it doing
great work. But, I need to hear some comments from all of you
confirming what I am seeing or telling me I am missing something.

Thanks to all, Frank







view thread (3+ messages)  latest in thread

Message-ID: <041c01be9ae7$668ea5a0$8355e5ce@base2inc.com>
Permalink:  ../041c01be9ae7$668ea5a0$8355e5ce@base2inc.com/
Also on:    postgresql.org/message-id/041c01be9ae7$668ea5a0$8355e5ce@base2inc.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: fmorton@base2inc.com
  Subject: Re: Slow Inserts Leads To Unable To Dump
  In-Reply-To: <041c01be9ae7$668ea5a0$8355e5ce@base2inc.com>
  References: <3736D569.F5A087E2@sinectis.com.ar> <041c01be9ae7$668ea5a0$8355e5ce@base2inc.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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