Re: How are locks managed in PG?

From: Thomas Kellerer <spam_eater(at)gmx(dot)net>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: How are locks managed in PG?
Date: 2008-12-19 13:13:13
Message-ID: gig6l9$7t0$1@ger.gmane.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Alvaro Herrera, 19.12.2008 13:49:
> We use an in-memory lock manager for table- and page-level locks. For
> shared tuple locks, they are spilled to disk on an ad-hoc storage system
> (pg_multixact) when there is more than one shared locker. (Exclusive
> locks and single locker shared locks are stored directly on the locked
> tuple.)
>
>> Oracle on the other hand stores the lock information directly in the data
>> block that is locked, thus the number of locks does not affect system
>> performance (in terms of managing them).
>>
>> I couldn't find any description on which strategy PG applies.
>
> None of the above. We're smarter than everyone else.

Thanks. This was the answer I was looking for :)

Thomas

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2008-12-19 13:43:35 Re: REVOKE CONNECT doesn't work in 8.3.5
Previous Message Alvaro Herrera 2008-12-19 12:49:58 Re: How are locks managed in PG?