From: Sibte Abbas <sibtay@gmail.com>
To: Mark Steben <msteben@autorevenue.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: row level locking
Date: Fri, 20 Jul 2007 14:54:55 -0400
Message-ID: <bd6a35510707201154r62884d1cp106aa1c88d4f46ec@mail.gmail.com> (raw)
In-Reply-To: <009c01c7cafa$874c2e60$b501a8c0@D1RPQZB1>
References: <009c01c7cafa$874c2e60$b501a8c0@D1RPQZB1>
On 7/20/07, Mark Steben <msteben@autorevenue.com> wrote:
>
> Hi listers,
>
> I have a table that is accessed by only one transaction. It has 1500 rows
> each time that it processes
>
> This transaction. As soon as this transaction ends, it waits 10 seconds and
> starts again.
>
> It has another maximum 1500 rows loaded. .
>
>
>
> My question is this: I believe a RowExclusive level lock is acquired 1500
> times during each transaction.
What type operations does the transaction performs on the table?
An exclusive row level lock is acquired only:
i) when a row is being updated, deleted or marked for deletion (Implicit lock)
ii) when SELECT FOR UPDATE query is executed on the table (to acquire
a share lock you can use SELECT FOR SHARE) (Explicit lock)
>
> Is this true? Is there a way to disable RowExclusive locks and reduce
> overhead since only this transaction
Consider running postgresql in single user mode. This would eradicate
all the Interprocess communication overheads.
>
> Accesses this table. I know there are ways to specify locking levels in
> other DBMSs. To page or table levels.
>
Postgresql handles page level locks implicitly, users do not have any
control over them.
regards,
--
Sibte Abbas
EnterpriseDB http://www.enterprisedb.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: sibtay@gmail.com, msteben@autorevenue.com
Subject: Re: row level locking
In-Reply-To: <bd6a35510707201154r62884d1cp106aa1c88d4f46ec@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox