| From: | Michael Fuhr <mike(at)fuhr(dot)org> |
|---|---|
| To: | Clodoaldo Pinto <clodoaldo(dot)pinto(at)gmail(dot)com> |
| Cc: | "pgsql-general postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: update functions locking tables |
| Date: | 2005-08-30 01:35:00 |
| Message-ID: | 20050830013500.GA54501@winnie.fuhr.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Aug 29, 2005 at 09:41:21PM -0300, Clodoaldo Pinto wrote:
>
> 26873 ? S 0:18 postgres: user database 127.0.0.1(38946) SELECT waiting
> 23973 ? S 0:22 postgres: user database 127.0.0.1(43396) SELECT waiting
> 31212 ? S 0:02 postgres: user database 127.0.0.1(60619) SELECT waiting
> 21601 ? S 0:00 postgres: user database 127.0.0.1(46770) SELECT waiting
>
> I've been trying for 3 days to figure out what is happening to no
> avail. What am i missing about transactions and MVCC? What could make
> a plpgsql update function lock a table? The indexes are default btree.
In general, writers shouldn't block readers. Have you examined
pg_locks? Do you know exactly what the blocked queries are, or can
you find out from pg_stat_activity (stats_command_string must be
enabled)? Are you doing any explicit locking (LOCK statement)?
--
Michael Fuhr
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-08-30 01:35:02 | Re: update functions locking tables |
| Previous Message | Clodoaldo Pinto | 2005-08-30 00:41:21 | update functions locking tables |