From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: FOR SHARE vs FOR UPDATE locks |
Date: | 2006-12-01 17:35:16 |
Message-ID: | 28702.1164994516@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> At what point is the exclusive lock released? When I create a new
> savepoint? On COMMIT of the entire transaction?
COMMIT, or rollback to a savepoint before the original shared lock
was taken.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-12-01 17:40:46 | Re: FOR SHARE vs FOR UPDATE locks |
Previous Message | Joshua D. Drake | 2006-12-01 17:34:37 | Re: FOR SHARE vs FOR UPDATE locks |
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2006-12-01 17:36:26 | Re: 8.2 Beta3-> RC1 upgrade |
Previous Message | Joshua D. Drake | 2006-12-01 17:34:37 | Re: FOR SHARE vs FOR UPDATE locks |