pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: Benedict Holland <benedict.m.holland@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Update blocking a select count(*)?
Date: Fri, 15 Jun 2012 15:38:39 -0500
Message-ID: <4FDB56FF0200002500048510@gw.wicourts.gov> (raw)
In-Reply-To: <CAD+mzoyBbX6z9erCNdp2gSP_xBLJOZQFiN7F-BJCS+-O1Sqbmg@mail.gmail.com>
References: <CAD+mzoxfm8Wa5hrekeakG_TYNd_dsTR3W3DPZEV90chuzh0N_A@mail.gmail.com>
	<CAEYLb_WqEecnjr5o0DoNh15kNF_FXGkErVKw7fCGM5xxNLmrvQ@mail.gmail.com>
	<4FDB3C0202000025000484E4@gw.wicourts.gov>
	<CAD+mzozTqB8YiFQsgxU5mMqVo01wxVE0yiwoMHD_uSfSApKt7Q@mail.gmail.com>
	<CAD+mzoykMCtGaAKN9jOyH=nDF1E=EORcs4DSAbbKwvt4jJEXsQ@mail.gmail.com>
	<4FDB40B702000025000484EE@gw.wicourts.gov>
	<CAD+mzowzWWea80Vthj_xNuiDOZzyqLpDZpjMgMSY-fHL-ewsCg@mail.gmail.com>
	<4FDB476A02000025000484F4@gw.wicourts.gov>
	<CAD+mzoxCUbQJb4XMuNizFXU9mVYcUg9myGomKXW1TwXuKnauTg@mail.gmail.com>
	<4FDB4DF602000025000484FE@gw.wicourts.gov>
	<CAD+mzoyBbX6z9erCNdp2gSP_xBLJOZQFiN7F-BJCS+-O1Sqbmg@mail.gmail.com>

Benedict Holland <benedict.m.holland@gmail.com> wrote:
 
> I ran the scripts on the page and both returned empty (though I
> have queries running and currently nothing blocks). I don't know
> what they should have been.
 
It only shows information on blocking, so the list should be empty
when there is none.  :-)  If it works as intended, it would have
shown the chain of blocking, from the update to the alter to the
select.
 
> The output was from PgAdmin3 which is a UI for postgres. I assume
> that they get this queried information from something inside of
> postgres as I can't imagine the query tool doing something other
> than querying the database for specs.
 
They are probably doing something internally which is somewhat
similar to the recursive query on that page.  It sounds like when
there is a chain or tree of blocking, they show the process at the
front of the parade, rather than the immediate blocker.  I can't say
that's right or wrong, but it should be documented so that people
can understand what they're looking at.  Even better would be to
make a nice graphical tree of the blocking, but that would be
getting pretty fancy.  :-)
 
-Kevin



view thread (18+ messages)

Message-ID: <4FDB56FF0200002500048510@gw.wicourts.gov>
Permalink:  ../4FDB56FF0200002500048510@gw.wicourts.gov/
Also on:    postgresql.org/message-id/4FDB56FF0200002500048510@gw.wicourts.gov

 · 

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: Kevin.Grittner@wicourts.gov, benedict.m.holland@gmail.com
  Subject: Re: Update blocking a select count(*)?
  In-Reply-To: <4FDB56FF0200002500048510@gw.wicourts.gov>

* 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