From: | Vitalii Tymchyshyn <tivv00(at)gmail(dot)com> |
---|---|
To: | Robert Ayrapetyan <robert(dot)ayrapetyan(at)comodo(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Performance die when COPYing to table with bigint PK |
Date: | 2011-08-01 09:06:36 |
Message-ID: | 4E366C9C.4040904@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
31.07.11 16:51, Robert Ayrapetyan написав(ла):
> Hello.
>
> I've found strange behavior of my pg installation (tested both 8.4 and
> 9.0 - they behave same) on FreeBSD platform.
> In short - when some table have PK on bigint field - COPY to that
> table from file becomes slower and slower as table grows. When table
> reaches ~5GB - COPY of 100k records may take up to 20 mins. I've
> experimented with all params in configs, moved indexes to separate hdd
> etc - nothing made any improvement. However, once I'm dropping 64 bit
> PK - COPY of 100k records passes in seconds. Interesting thing - same
> table has other indexes, including composite ones, but none of them
> include bigint fields, that's why I reached decision that bug
> connected with indexes on bigint fields only.
I did see this behavior, but as for me it occurs for UNIQUE indexes only
(including PK), not dependent on field type.
You can check this by dropping PK and creating it as a regular
non-unique index.
Best regards, Vitalii Tymchyshyn
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Ayrapetyan | 2011-08-01 09:15:52 | Re: Performance die when COPYing to table with bigint PK |
Previous Message | Simon Riggs | 2011-08-01 08:54:45 | Re: Performance die when COPYing to table with bigint PK |