Re: [SQL] Slow Inserts Leads To Unable To Dump

From: Engard Ferenc <fery(at)pons(dot)sote(dot)hu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: [SQL] Slow Inserts Leads To Unable To Dump
Date: 1999-05-13 12:17:21
Message-ID: Pine.LNX.4.02.9905131409210.320-100000@domesticus.sote.hu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On Mon, 10 May 1999, Tom Lane wrote:

>"Frank Morton" <fmorton(at)base2inc(dot)com> writes:
>> 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,
[...]
>It does seem that your installation is remarkably slow; other people
>are working with tables exceeding 2Gb and don't seem unhappy about

Try 'copy': for cc. 170,000 records the import took me about 5-15
mins (I don't remember) on a P100 with 16MB of RAM. From the
insert-stuff it should not be a big deal to convert to tab-separated
text.

Circum

__ @
/ \ _ _ Engard Ferenc
l | ( \ / | | (\/) mailto:s-fery(at)kkt(dot)sote(dot)hu
\__/ | | \_ \_/ I I http://pons.sote.hu/~s-fery

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Tom Lane 1999-05-13 14:11:32 Re: [SQL] VARCHAR(50), CHAR(50) or TEXT ?
Previous Message Brett W. McCoy 1999-05-13 11:49:23 Re: [SQL] VARCHAR(50), CHAR(50) or TEXT ?