pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jan Wieck <JanWieck@Yahoo.com>
To: Stephan Szabo <sszabo@megazone23.bigpanda.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Kevin Brown <kevin@sysexperts.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: [PERFORM] Foreign key performance
Date: Fri, 25 Apr 2003 15:52:16 -0400
Message-ID: <3EA991F0.A201AC38@Yahoo.com> (raw)
References: <20030418073753.B1912-100000@megazone23.bigpanda.com>

Stephan Szabo wrote:
> 
> [Not sure this really is relevant for -performance at this point]
> 
> On Thu, 17 Apr 2003, Stephan Szabo wrote:
> 
> > On Fri, 18 Apr 2003, Tom Lane wrote:
> >
> > > Stephan Szabo <sszabo@megazone23.bigpanda.com> writes:
> > > > It appears (from some not terribly scientific experiments - see below)
> > > > that it's likely to be related to managing the deferred trigger queue
> > > > given that in my case at least running the constraints non-deferred was
> > > > negligible in comparison.
> > >
> > > At one time the deferred-trigger queue had an O(N^2) behavioral problem
> > > for large N = number of pending trigger events.  But I thought we'd
> > > fixed that.  What's the test case exactly?  Can you get a profile with
> > > gprof?
> >
> > I'm going to tomorrow hopefully - but it looks to me that we fixed one, but
> 
> Argh. I'm getting that state where gprof returns all 0s for times.  I'm
> pretty sure this has come up before along with how to get it to work, but
> I couldn't find it in the archives. Someday I'll learn how to use gprof. :(

You have to save and restore the timers around the fork() under Linux.


Jan

-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #




view thread (18+ messages)  latest in thread

Message-ID: <3EA991F0.A201AC38@Yahoo.com>
Permalink:  ../3EA991F0.A201AC38@Yahoo.com/
Also on:    postgresql.org/message-id/3EA991F0.A201AC38@Yahoo.com

 · 

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: JanWieck@Yahoo.com, sszabo@megazone23.bigpanda.com, tgl@sss.pgh.pa.us, kevin@sysexperts.com, pgsql-hackers@postgresql.org
  Subject: Re: [PERFORM] Foreign key performance
  In-Reply-To: <3EA991F0.A201AC38@Yahoo.com>

* 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