Re: COPY FROM STDIN instead of INSERT

From: Shane Ambler <pgsql(at)007Marketing(dot)com>
To: ilejn(at)yandex(dot)ru
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: COPY FROM STDIN instead of INSERT
Date: 2006-10-18 12:06:16
Message-ID: 453618B8.1060302@007Marketing.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Ilja Golshtein wrote:

>> Sounds like your working with an existing database - if you are starting
>>from scratch (inserting data into an empty database) then there are
>> other things that can help too.
>
> I am working with existing database, though I am interested what "other things" you mean.
>
Basically when adding data to a table some of the time spent inserting
is spent updating indexes.

When starting a database from scratch it is much faster to import the
data and then create the indexes. The time to create index on a full
table is less than the extra time from each index update from the
inserts. The more indexes to update the more time updating indexes takes.

The problem with a live database is removing the indexes slows down
current users and if you are adding 2,000 rows to a table that already
has 5,000,000 rows in it then you will loose the benefit.

--

Shane Ambler
Postgres(at)007Marketing(dot)com

Get Sheeky @ http://Sheeky.Biz

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bill Moran 2006-10-18 12:15:06 Can't get ECPG to connect (was Re: Urgen help required)
Previous Message Magnus Hagander 2006-10-18 12:06:10 Re: [HACKERS] query log corrupted-looking entries