From: | Erik Jones <erik(at)myemma(dot)com> |
---|---|
To: | Reg Me Please <regmeplease(at)gmail(dot)com> |
Cc: | "Josh Tolley" <eggyknap(at)gmail(dot)com>, "Postgres General" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: COPY ... FROM and index usage |
Date: | 2007-11-04 15:21:41 |
Message-ID: | 19308F9C-569B-42E0-B91E-EC5E2DAEBC87@myemma.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Nov 4, 2007, at 9:15 AM, Reg Me Please wrote:
> Il Sunday 04 November 2007 14:59:10 Josh Tolley ha scritto:
>> On 11/4/07, Reg Me Please <regmeplease(at)gmail(dot)com> wrote:
>>> Hi all.
>>>
>>> I'd like to know whether the indexes on a table are updated or
>>> not during
>>> a "COPY ... FROM" request.
>>>
>>> That is, should I drop all indexes during a "COPY ... FROM" in
>>> order to
>>> gain the maximum speed to load data?
>>>
>>> Thanks.
>>
>> Although questions of "which is faster" often depend very heavily on
>> the data involved, the database schema, the hardware, etc., typically
>> people find it best to drop all indexes during a large import and
>> recreate them afterward.
>>
>> - Josh/eggyknap
>
> This sounds very reasonable to me.
> But the first question remains unanswered:
>
> Are the indexes updated during the COPY ... FROM ?
Of course. Why would think that data could be inserted into a table
by any means without it updating the table's indexes? That would
make the index worthless.
Erik Jones
Software Developer | Emma®
erik(at)myemma(dot)com
800.595.4401 or 615.292.5888
615.292.0777 (fax)
Emma helps organizations everywhere communicate & market in style.
Visit us online at http://www.myemma.com
From | Date | Subject | |
---|---|---|---|
Next Message | Reg Me Please | 2007-11-04 15:26:49 | Re: COPY ... FROM and index usage |
Previous Message | Reg Me Please | 2007-11-04 15:15:33 | Re: COPY ... FROM and index usage |