| From: | "Steinar H(dot) Gunderson" <sgunderson(at)bigfoot(dot)com> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Locking in PostgreSQL? |
| Date: | 2006-12-06 13:31:04 |
| Message-ID: | 20061206133104.GA9537@uio.no |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-performance |
On Wed, Dec 06, 2006 at 08:26:45AM -0500, Dave Cramer wrote:
> Apparently I've completely misunderstood MVCC then.... My
> understanding is that unless you do a select ... for update then
> update the rows will not be locked .
The discussion was about updates, not selects. Selects do not in general lock
(except for ... for update, as you say).
To (partially) answer the original question: The number of columns updated
does not matter for the locking situation.
/* Steinar */
--
Homepage: http://www.sesse.net/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Schiltknecht | 2006-12-06 13:42:32 | Re: [PERFORM] Locking in PostgreSQL? |
| Previous Message | Dave Cramer | 2006-12-06 13:26:45 | Re: [PERFORM] Locking in PostgreSQL? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Schiltknecht | 2006-12-06 13:42:32 | Re: [PERFORM] Locking in PostgreSQL? |
| Previous Message | Dave Cramer | 2006-12-06 13:26:45 | Re: [PERFORM] Locking in PostgreSQL? |