| From: | Shay Moreno <moreno(at)tdk(dot)dk> |
|---|---|
| To: | "'Manohar(dot)K (GM Systems)'" <manohark(at)elgi(dot)jet(dot)co(dot)in>, "'esavas(at)mac(dot)com'" <esavas(at)mac(dot)com>, pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: Locking a Table |
| Date: | 2001-04-27 07:11:16 |
| Message-ID: | 5D38890DAE46D41186A800508B6F7187026FFE58@oestmb010-b0.tdk.dk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
> How to lock a table during transaction processing in PostgreSQL 7.0.2
In the reference manual at
http://postgresql.org/users-lounge/docs/7.1/reference/ you will find the
LOCK command,
http://postgresql.org/users-lounge/docs/7.1/reference/sql-lock.html. Again
you can find this information thru the users' lounge at
http://postgresql.org./
But usually you won't need to lock explicitly. Locking will be done
automagically whenever you access any data. The locks will be the minimum
necessary and sufficient to keep data integrity, and they will be release at
the end of the transaction: COMMIT, ROLLBACK or a program failure.
--
_
/ \ Leandro Guimarães Faria Corcete Dutra +55 (11) 3040 8913
\ / Amdocs Brasil Ltda at Tele Danmark +45 3387 5214
X http://geocities.com./lgdutra/ mailto:leandrod(at)amdocs(dot)com
/ \ Campanha fita ASCII mailto:moreno(at)tdk(dot)dk
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Phill Kenoyer | 2001-04-27 07:44:56 | plpgsql locate provider by zip code |
| Previous Message | Joel Burton | 2001-04-26 18:48:15 | Re: DROP COLUMN ? |