Hi.
My simple testcase is:
> Testcase may be as simple as:
>
> CREATE TABLESPACE tblsp_ix LOCATION '/some_dedicated_hdd'
>
> CREATE TABLE tp_req
> (
>id bigint PRIMARY KEY USING INDEX TABLESPACE tblsp_ix,
>arrived timestamp NOT NULL,
>real_ip inet,
>tp_id integer NOT NULL,
>ac
Hi,
What happens if you drop other indices with a similar size before starting the
copy? It might just be the additional io-load (causing more checkpoints, more
random io, etc) is causing the problems.
Could you share your config and hw info?
Greetings,
Andres
--
Sent via pgsql-bugs mailing
On Mon, Aug 1, 2011 at 8:25 AM, simon wrote:
> Could be that its storing the wrong kind of plan on the RI trigger for PK.
No, not that. Will look elsewhere.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pg
On Sun, Jul 31, 2011 at 2:47 PM, Robert wrote:
> 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. Wh
