Re: Insert performance for large transaction with multiple COPY FROM - Mailing list pgsql-performance

From Claudio Freire
Subject Re: Insert performance for large transaction with multiple COPY FROM
Date
Msg-id CAGTBQpY4EF=B-5dPZLs5+nDQTxY2u166sR8AY_GNro2uyt1VNg@mail.gmail.com
Whole thread Raw
In response to Re: Insert performance for large transaction with multiple COPY FROM  (Horst Dehmer <horst.dehmer@gmail.com>)
List pgsql-performance
On Sat, Jan 12, 2013 at 7:41 PM, Horst Dehmer <horst.dehmer@gmail.com> wrote:
> Since the complete schema (of about 300 tables) is generated, I will just try char(20) instead of numeric(20) in the
nextdays to see if it makes any difference. Which I somehow doubt. 

I think that might just make it worse.

Well, maybe the others were right, and it's just that you're hitting
the disk on that particular table.

That, or it's all those CHECK constraints. Have you tried removing the
CHECK constraints (they're a heapload of function calls)


pgsql-performance by date:

Previous
From: Horst Dehmer
Date:
Subject: Re: Insert performance for large transaction with multiple COPY FROM
Next
From: Alexandre de Arruda Paes
Date:
Subject: From TODO: Simplify creation of partitioned tables