Message-ID: <4E366C9C.4040904@gmail.com>
Date: Mon, 01 Aug 2011 12:06:36 +0300
From: Vitalii Tymchyshyn <tivv00@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
	rv:1.9.2.18) Gecko/20110617 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: Robert Ayrapetyan <robert.ayrapetyan@comodo.com>
CC: pgsql-performance@postgresql.org
Subject: Re: Performance die when COPYing to table with bigint PK
References: 
 <CAAboi9sk0EnbS23-tr86X9i7LdHTfdbTP4aa7r2q7NpWKaHWPA@mail.gmail.com>
In-Reply-To: 
 <CAAboi9sk0EnbS23-tr86X9i7LdHTfdbTP4aa7r2q7NpWKaHWPA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

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