| From: | "Allan Kamau" <kamauallan(at)gmail(dot)com> |
|---|---|
| To: | "Thomas Kellerer" <spam_eater(at)gmx(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: How are locks managed in PG? |
| Date: | 2008-12-19 10:04:04 |
| Message-ID: | ab1ea6540812190204m4a5ef309xbff0ff9270eab073@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Postgres by default uses the MVCC (Multiversion Concurrency Control,
MVCC) for concurrency control. This is a large topic and may require
more explanation than a simple email response would easily provide.
The well written PostgreSQL documentation has good explanation on this
topic (http://www.postgresql.org/docs/8.3/interactive/mvcc.html)
If you explicity require table and row level locking the above link
will provide answers on these too.
Allan.
On Fri, Dec 19, 2008 at 10:32 AM, Thomas Kellerer <spam_eater(at)gmx(dot)net> wrote:
> Hi,
>
> I have a question on how PG manages lock information.
> Does this go through a central "lock manager" that manages the information
> which row is locked by which transactioni. Or is the lock information stored
> directly within the data blocks (so no central "data structure" would be
> needed)
>
> Thanks
> Thomas
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erwin Moller | 2008-12-19 10:28:04 | create a 'range' of dates/numbers? |
| Previous Message | Richard Huxton | 2008-12-19 09:58:57 | Re: Hi iam the beginner |