lock conflicting with another

[Amir Zicherman]

what does it mean when one lock mode conflicts with another like is
says in the documentation? can somebody explain and maybe give an
example.

thanx, amir

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to ma*******@postgresql.org so that your
message can get through to the mailing list cleanly

[Tom Lane]

Amir Zicherman <am************@gmail.com> writes:

what does it mean when one lock mode conflicts with another

It means that a holder of the one lock type will block a requestor
of the other lock type (on the same lockable object, of course).

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match