pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedRow Level Locking !!
7+ messages / 7 participants
[nested] [flat]
* Row Level Locking !!
@ 2001-06-20 05:46 Mahesh Guleria <mahesh@himline.com>
0 siblings, 1 reply; 7+ messages in thread
From: Mahesh Guleria @ 2001-06-20 05:46 UTC (permalink / raw)
To: pgsql-sql@postgresql.org; pgsql-admin
Is it possible that we can use row level locking in postgres.
If "yes",
then but is the proceedure and where i can found the documentation.
-MG
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Row Level Locking !!
@ 2001-06-20 11:03 Christof Glaser <gcg@gl.aser.de>
parent: Mahesh Guleria <mahesh@himline.com>
0 siblings, 1 reply; 7+ messages in thread
From: Christof Glaser @ 2001-06-20 11:03 UTC (permalink / raw)
To: Mahesh Guleria <mahesh@himline.com>; pgsql-sql@postgresql.org; pgsql-admin
On Wednesday, 20. June 2001 07:46, Mahesh Guleria wrote:
> Is it possible that we can use row level locking in postgres.
> If "yes",
> then but is the proceedure and where i can found the documentation.
There is "something better than row level locking" called MVCC, or
Multi Version Concurrency Control for short.
See Chapter 9 of the User Guide:
http://www.postgresql.org/idocs/index.php?mvcc.html
Hope that helps,
Christof
--
gl.aser . software engineering . internet service
http://gl.aser.de/ . Planckstraße 7 . D-39104 Magdeburg
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: [SQL] Re: Row Level Locking !!
@ 2001-06-20 14:47 Roberto Mello <rmello@cc.usu.edu>
parent: Christof Glaser <gcg@gl.aser.de>
0 siblings, 0 replies; 7+ messages in thread
From: Roberto Mello @ 2001-06-20 14:47 UTC (permalink / raw)
To: Christof Glaser <gcg@gl.aser.de>; +Cc: Mahesh Guleria <mahesh@himline.com>; pgsql-sql@postgresql.org; pgsql-admin
On Wed, Jun 20, 2001 at 01:03:49PM +0200, Christof Glaser wrote:
> On Wednesday, 20. June 2001 07:46, Mahesh Guleria wrote:
>
> > Is it possible that we can use row level locking in postgres.
> > If "yes",
> > then but is the proceedure and where i can found the documentation.
I'd like to point out (for the new users around) that PostgreSQL
has had Multi Version Concurrency Control for quite some time. You don't
have to do anything special to use it. It's the default to handle
concurrency.
-Roberto
--
+----| http://fslc.usu.edu USU Free Software & GNU/Linux Club |------+
Roberto Mello - Computer Science, USU - http://www.brasileiro.net
http://www.sdl.usu.edu - Space Dynamics Lab, Developer
* * * <- Tribbles . . . <- Tribbles after a haircut
^ permalink raw reply [nested|flat] 7+ messages in thread
* Row level Locking
@ 2003-03-03 13:04 Raj Sundar <rajsundar@epmltd.com>
0 siblings, 0 replies; 7+ messages in thread
From: rajsundar@epmltd.com @ 2003-03-03 13:04 UTC (permalink / raw)
To: pgsql-admin
Sir,
Any body , How can I do Row Level Locking in postgreSQL while selecting a row ?
^ permalink raw reply [nested|flat] 7+ messages in thread
* row level locking
@ 2007-07-20 18:19 Mark Steben <msteben@autorevenue.com>
0 siblings, 2 replies; 7+ messages in thread
From: Mark Steben @ 2007-07-20 18:19 UTC (permalink / raw)
To: pgsql-admin
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.
Is this true? Is there a way to disable RowExclusive locks and reduce
overhead since only this transaction
Accesses this table. I know there are ways to specify locking levels in
other DBMSs. To page or table levels.
We are currently at version 7.4.5.
Thank you for your time,
Mark Steben
Senior Database Administrator
@utoRevenueT
A Dominion Enterprises Company
480 Pleasant Street
Suite B200
Lee, MA 01238
413-243-4800 Home Office
413-243-4809 Corporate Fax
msteben <blocked::mailto:name@autorevenue.com> @autorevenue.com
Visit our new website at
<blocked::http://www.autorevenue.com/; www.autorevenue.com
IMPORTANT: The information contained in this e-mail message is confidential
and is intended only for the named addressee(s). If the reader of this
e-mail message is not the intended recipient (or the individual responsible
for the delivery of this e-mail message to the intended recipient), please
be advised that any re-use, dissemination, distribution or copying of this
e-mail message is prohibited. If you have received this e-mail message in
error, please reply to the sender that you have received this e-mail message
in error and then delete it. Thank you.
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: row level locking
@ 2007-07-20 18:54 Sibte Abbas <sibtay@gmail.com>
parent: Mark Steben <msteben@autorevenue.com>
1 sibling, 0 replies; 7+ messages in thread
From: Sibte Abbas @ 2007-07-20 18:54 UTC (permalink / raw)
To: Mark Steben <msteben@autorevenue.com>; +Cc: pgsql-admin
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
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: row level locking
@ 2007-07-21 11:26 Simon Riggs <simon@2ndquadrant.com>
parent: Mark Steben <msteben@autorevenue.com>
1 sibling, 0 replies; 7+ messages in thread
From: Simon Riggs @ 2007-07-21 11:26 UTC (permalink / raw)
To: Mark Steben <msteben@autorevenue.com>; +Cc: pgsql-admin
On Fri, 2007-07-20 at 14:19 -0400, Mark Steben wrote:
> We are currently at version 7.4.5.
You should upgrade if you want better performance and scalability.
Or maybe you should just use COPY?
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
^ permalink raw reply [nested|flat] 7+ messages in thread
end of thread, other threads:[~2007-07-21 11:26 UTC | newest]
Thread overview: 7+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2001-06-20 05:46 Row Level Locking !! Mahesh Guleria <mahesh@himline.com>
2001-06-20 11:03 ` Christof Glaser <gcg@gl.aser.de>
2001-06-20 14:47 ` Roberto Mello <rmello@cc.usu.edu>
2003-03-03 13:04 Row level Locking Raj Sundar <rajsundar@epmltd.com>
2007-07-20 18:19 row level locking Mark Steben <msteben@autorevenue.com>
2007-07-20 18:54 ` Re: row level locking Sibte Abbas <sibtay@gmail.com>
2007-07-21 11:26 ` Re: row level locking Simon Riggs <simon@2ndquadrant.com>
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