| From: | Raimon Fernandez <coder(at)montx(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michał Roszka <mike(at)if-then-else(dot)pl>, pgsql-general List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: SELECT is immediate but the UPDATE takes forever |
| Date: | 2010-12-09 03:41:48 |
| Message-ID: | 79F1DE5D-9E90-4942-A90C-AB9A5B6F300D@montx.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-interfaces |
On 7dic, 2010, at 16:37 , Tom Lane wrote:
>> Quoting Raimon Fernandez <coder(at)montx(dot)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?
no, there's no lock, blocked, ... I'm the only user connected with my developer test database and I'm sure there are no locks, and more sure after looking at pg_locks :-)
thanks,
r.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Raimon Fernandez | 2010-12-09 03:58:55 | Re: SELECT is immediate but the UPDATE takes forever |
| Previous Message | Raimon Fernandez | 2010-12-09 03:40:13 | use a variable name for an insert in a trigger for an audit |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Raimon Fernandez | 2010-12-09 03:58:55 | Re: SELECT is immediate but the UPDATE takes forever |
| Previous Message | Raimon Fernandez | 2010-12-09 03:40:13 | use a variable name for an insert in a trigger for an audit |