From: | "Jose' Soares Da Silva" <sferac(at)bo(dot)nettuno(dot)it> |
---|---|
To: | questions postgres <pgsql-questions(at)postgresql(dot)org> |
Cc: | hackers postgres <pgsql-hackers(at)postgresql(dot)org> |
Subject: | locks |
Date: | 1998-05-11 14:49:37 |
Message-ID: | Pine.LNX.3.96.980511144848.652A-100000@proxy.bazzanese.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi all,
After almost one year using PostgreSQL, I'm still discovering things about
locks, we have little documentation about it:
I know that one can lock a table in the following ways:
* BEGIN statement:
If you don't explicit lock a table using LOCK statement, it will be
implicit locked only at first UPDATE, INSERT or DELETE operation.
* DECLARE statement:
Currently, PostgreSQL doesn't support READ ONLY cursors, once a cursor
is declared, other users can only read data referenced by cursor.
Write operations to the referenced table like UPDATE, INSERT,
DELETE or DROP aren't allowed until the end of transaction.
* LOCK statement:
LOCK don't allows read access to locked tables by the other users.
If another user try to SELECT a locked table, he must attend
until the locked table is released.
Just wondering if there are other ways to lock tables.
Any replay will be appreciate. Thanks, Jose'
From | Date | Subject | |
---|---|---|---|
Next Message | Brett McCormick | 1998-05-11 14:57:23 | Re: [HACKERS] Re: [PATCHES] Try again: S_LOCK reduced contentionh] |
Previous Message | Tom Lane | 1998-05-11 14:49:11 | Re: [HACKERS] Re: [PATCHES] Try again: S_LOCK reduced contentionh] |