:[EMAIL PROTECTED]
Sent: 27 June 2005 14:05
To: Praveen Raja
Cc: pgsql-performance@postgresql.org
Subject: RE: [PERFORM] Insert performance vs Table size
Hi,
At 13:50 27/06/2005, Praveen Raja wrote:
Just to clear things up a bit, the scenario that I'm interested in is a
table with a large number
Hi,
At 11:50 28/06/2005, Praveen Raja wrote:
I assume you took size to mean the row size?
Nope, the size of the table.
What I really meant was
does the number of rows a table has affect the performance of new
inserts into the table (just INSERTs) all other things remaining
constant. Sorry
Praveen Raja [EMAIL PROTECTED] writes:
I know that having indexes on the table adds an overhead but again does
this overhead increase (for an INSERT operation) with the number of rows
the table contains?
Typical index implementations (such as b-tree) have roughly O(log N)
cost to insert or
Praveen Raja:
I think the size of a table don't affect the speed of inserts
into it.Because PostgreSQL just doing something like append on the data files.
But the index do speed-down the inserts. Because PostgreSQL should
maintain the index when doing inserts.
Hi,
At 13:24 27/06/2005, Praveen Raja wrote:
I'm wondering if and how the size of a table affects speed of inserts
into it? What if the table has indexes, does that alter the answer?
Many parameters will affect the result:
- whether there are any indexes (including the primary key, unique
of the table play a role in determining insert performance (and I mean
only insert performance)?
-Original Message-
From: Jacques Caron [mailto:[EMAIL PROTECTED]
Sent: 27 June 2005 13:40
To: Praveen Raja
Cc: pgsql-performance@postgresql.org
Subject: Re: [PERFORM] Insert performance vs Table size
Hi
Hi,
At 13:50 27/06/2005, Praveen Raja wrote:
Just to clear things up a bit, the scenario that I'm interested in is a
table with a large number of indexes on it (maybe 7-8).
If you're after performance you'll want to carefully consider which indexes
are really useful and/or redesign your