How to specify explicit locking while creating a table in PostgreSQL

Question

What is the default locking mechanism in PostgresSQL when we create a table ? is it row, page, table level or something else?

Is it possible to specify row level locking when we create a table ? something like below in Sybase.

CREATE TABLE user 
(...)
LOCK DATRAROWS

Or do we not need to specify any locking strategy and leave it to Postgres to choose the best while we dealing CRUD ?

Cheers!

I believe postgres always uses the least intrusive locking mechanism possible -- MVCC row level locking, in most cases. — Frank Farmer
– Frank Farmer, Commented Apr 30, 2011 at 0:29
I'm coming from Sybase space, where we used to explicitly set lock datarows, and here in my specific use case, I don't want Postgres to use anything other than row level locking. Now I understand things are bit different in PGSql :-) — sojin
– sojin, Commented May 1, 2011 at 14:28

Mike Sherrill 'Cat Recall' · Accepted Answer · 2011-04-30 00:49:55Z

1

There isn't anything you can specify at CREATE TABLE time for PostgreSQL. At run time, you can select rows FOR UPDATE or FOR SHARE. If you're coming to PostgreSQL from another platform, you should skim the docs on concurrency control.

answered Apr 30, 2011 at 0:49

Mike Sherrill 'Cat Recall'

96.6k20 gold badges134 silver badges195 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Ketema · Accepted Answer · 2011-04-30 04:35:47Z

1

There is no locking when you create a table. Locking can be read here: http://www.postgresql.org/docs/9.0/static/explicit-locking.html

answered Apr 30, 2011 at 4:35

Ketema

6,7883 gold badges23 silver badges24 bronze badges

Collectives™ on Stack Overflow

How to specify explicit locking while creating a table in PostgreSQL

2 Answers 2

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related