pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kelly Burkhart <kelly@tradebotsystems.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: 8.x index insert performance
Date: Thu, 10 Nov 2005 17:18:14 -0500
Message-ID: <12266.1131661094@sss.pgh.pa.us> (raw)
In-Reply-To: <1131655202.7514.46.camel@krb06.tradebot.com>
References: <6EE64EF3AB31D5448D0007DD34EEB3417DD725@Herge.rcsinc.local>
	<20051031193547.GA3311@mark.mielke.cc>
	<18647.1130790629@sss.pgh.pa.us>
	<1130792391.7026.55.camel@krb06.tradebot.com>
	<19065.1130793527@sss.pgh.pa.us>
	<1130852029.7026.88.camel@krb06.tradebot.com>
	<24845.1130852730@sss.pgh.pa.us>
	<1131655202.7514.46.camel@krb06.tradebot.com>

Kelly Burkhart <kelly@tradebotsystems.com> writes:
> I've finally gotten around to profiling the back end.

Thanks for following up.

The sudden appearance of pg_detoast_datum() in the top ten in the third
profile is suspicious.  I wouldn't expect that to get called at all,
really, during a normal COPY IN process.  The only way I can imagine it
getting called is if you have index entries that require toasting, which
seems a bit unlikely to start happening only after 60 million rows.
Is it possible that the index keys are getting longer and longer as your
test run proceeds?

Could you send me (off list) the complete gprof output files?

			regards, tom lane



view thread (29+ messages)  latest in thread

Message-ID: <12266.1131661094@sss.pgh.pa.us>
Permalink:  ../12266.1131661094@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/12266.1131661094@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, kelly@tradebotsystems.com
  Subject: Re: 8.x index insert performance
  In-Reply-To: <12266.1131661094@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox