From: | "Christian Leclerc" <cleclerc(at)ilog(dot)fr> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: How to optimize insert statements ? |
Date: | 2007-07-25 10:48:17 |
Message-ID: | 1F31510056BF344C8D1076017C1367FA0FCF2A@parmbx02.ilog.biz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Hello Tom,
Thanks for your reply and advise. I understand in your email that the
use of a sequence object will increase the performance of my trigger.
Therefore I'm going to replace that in my code immediately. Anyway, my
problem is not exactly the performances; it's more the insertion time
growing. Indeed I don't understand why the insertion time grows
"exponentially" with my single transaction. If I split my objects
insertion into several transactions (instead of one), the problem seems
to disappear. Would you see any reasons linked to the Postgres
transactions explaining this insertion time growing ?
Regards,
Christian
-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Tuesday, July 24, 2007 4:33 PM
To: Christian Leclerc
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: [NOVICE] How to optimize insert statements ?
"Christian Leclerc" <cleclerc(at)ilog(dot)fr> writes:
> I'm encountering a performance issue with insert statements.
It looks to me like your trigger is the entire cause of the slowness.
I think you would be well advised to get rid of it and use a serial
column (ie a sequence object) instead of a handmade, poorly performing
substitute for sequences.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Sean Davis | 2007-07-25 11:03:40 | Re: How to optimize insert statements ? |
Previous Message | Michael Glaesemann | 2007-07-25 06:00:14 | Re: check (constraint) on point data type? |