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

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michał Roszka <mike@if-then-else.pl>
Cc: Raimon Fernandez <coder@montx.com>
Cc: pgsql-general List <pgsql-general@postgresql.org>
Subject: Re: SELECT is immediate but the UPDATE takes forever
Date: Tue, 07 Dec 2010 10:37:40 -0500
Message-ID: <22559.1291736260@sss.pgh.pa.us> (raw)
In-Reply-To: <20101207154537.81utnyfeo00cwgwg@horde.iq.pl>
References: <92781008-8A70-42CE-A49B-6EE67103FACB@montx.com>
	<FC6CBC8C-A398-4835-B3A3-C16C6F4F62D9@pgedit.com>
	<E084987E-A212-4B70-8CFF-D83AA00629C5@montx.com>
	<C670629A-1E54-4F80-9497-6CCAC1A8BDC0@montx.com>
	<20091026231516.GN8812@alvh.no-ip.org>
	<4AE62E21.7040600@hogranch.com>
	<66F15D69-75E5-4D8E-84F8-2F21E09BBA98@pgedit.com>
	<9A9F2678-36B9-42A2-91B2-69076065E8EB@montx.com>
	<20091027134158.GB4876@alvh.no-ip.org>
	<4AB34FE9-CC23-48BE-B905-6478304E0E5B@montx.com>
	<20091027140657.GF4876@alvh.no-ip.org>
	<B7382F17-63B5-49D0-8E39-0F46F9243C95@montx.com>
	<B1EA5872-6E57-46A8-BF35-3192707A5C0F@montx.com>
	<A8F7FAA5-A817-4CCE-BA06-BF28B5534AC7@montx.com>
	<4B057205.6000203@gmail.com>
	<A86C9188-4DAC-4EC4-86BD-0B483287BC71@montx.com>
	<322BBEA5-A328-4197-971E-95359D8FD7F3@montx.com>
	<4B05A8D4.7020500@gmail.com>
	<6A231EA8-5255-47F3-BECB-9BFBD700044C@montx.com>
	<20879F35-6940-4272-988E-703E610C6212@montx.com>
	<57FE8BF9-5E03-4F5A-9BBA-A06118CC2E3B@pgedit.com>
	<0AADF4A5-E795-4F2D-AA2B-A4E1A4B! ! D 9D93 @montx.com>
	<AC4{ h@ <20101207154537.81utnyfeo00cwgwg@horde.iq.pl>

=?utf-8?b?TWljaGHFgg==?= Roszka <mike@if-then-else.pl> writes:
> Quoting Raimon Fernandez <coder@montx.com>:
>> I want to understand why one of my postgresql functions takes an
>> eternity to finish.

> Maybe there is any check or constraint on belongs_to_compte_id.comptes that
> might take longer?

Or maybe the UPDATE is blocked on a lock ... did you look into
pg_stat_activity or pg_locks to check?

			regards, tom lane



view thread (10+ messages)  latest in thread

Message-ID: <22559.1291736260@sss.pgh.pa.us>
Permalink:  ../22559.1291736260@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/22559.1291736260@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-interfaces@postgresql.org
  Cc: tgl@sss.pgh.pa.us, mike@if-then-else.pl, coder@montx.com, pgsql-general@postgresql.org
  Subject: Re: SELECT is immediate but the UPDATE takes forever
  In-Reply-To: <22559.1291736260@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