pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Row Level Locking !!
5+ messages / 5 participants
[nested] [flat]

* Row Level Locking !!
@ 2001-06-20 05:46  Mahesh Guleria <mahesh@himline.com>
  0 siblings, 1 reply; 5+ messages in thread

From: Mahesh Guleria @ 2001-06-20 05:46 UTC (permalink / raw)
  To: pgsql-sql; pgsql-admin@postgresql.org

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] 5+ 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; 5+ messages in thread

From: Christof Glaser @ 2001-06-20 11:03 UTC (permalink / raw)
  To: Mahesh Guleria <mahesh@himline.com>; pgsql-sql; pgsql-admin@postgresql.org

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] 5+ 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; 5+ 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; pgsql-admin@postgresql.org

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] 5+ messages in thread

* row level locking?
@ 2001-09-10 15:25  Jeff Barrett <jbarrett@familynetwork.com>
  0 siblings, 1 reply; 5+ messages in thread

From: Jeff Barrett @ 2001-09-10 15:25 UTC (permalink / raw)
  To: pgsql-sql

I have an update statement (no transaction controls surround these
statements):

update sessions set sessdate = 0 where sessid in ( long list of ids);

How long will the rows being updated be locked for this statement? Will all
be locked until all updates are completed or will the row locking only occur
for each row being updated?

If I have a statement like:

update sessions set sessdate = 0 where datetime < 10000; (this would be the
same criteria that created the list used above)

How long will each row be locked for?

These queries can be updating a good number of rows ( > 10,000) every 10
minutes and I need to figure out how signifigant of an impact the locking
occuring in those updates can be.





^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: row level locking?
@ 2001-09-10 17:18  Stephan Szabo <sszabo@megazone23.bigpanda.com>
  parent: Jeff Barrett <jbarrett@familynetwork.com>
  0 siblings, 0 replies; 5+ messages in thread

From: Stephan Szabo @ 2001-09-10 17:18 UTC (permalink / raw)
  To: Jeff Barrett <jbarrett@familynetwork.com>; +Cc: pgsql-sql

On Mon, 10 Sep 2001, Jeff Barrett wrote:

> I have an update statement (no transaction controls surround these
> statements):
> 
> update sessions set sessdate = 0 where sessid in ( long list of ids);
> 
> How long will the rows being updated be locked for this statement? Will all
> be locked until all updates are completed or will the row locking only occur
> for each row being updated?

AFAIK until the end of statement (since it's wrapped in an implicit
transaction)

> If I have a statement like:
> 
> update sessions set sessdate = 0 where datetime < 10000; (this would be the
> same criteria that created the list used above)

Should be the same I would guess.




^ permalink  raw  reply  [nested|flat] 5+ messages in thread


end of thread, other threads:[~2001-09-10 17:18 UTC | newest]

Thread overview: 5+ 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>
2001-09-10 15:25 row level locking? Jeff Barrett <jbarrett@familynetwork.com>
2001-09-10 17:18 ` Re: row level locking? Stephan Szabo <sszabo@megazone23.bigpanda.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