Alvaro Herrera f88d4cfc9d Setup error context callback for transaction lock waits ...

With this in place, a session blocking behind another one because of
tuple locks will get a context line mentioning the relation name, tuple
TID, and operation being done on tuple.  For example:

LOG:  process 11367 still waiting for ShareLock on transaction 717 after 1000.108 ms
DETAIL:  Process holding the lock: 11366. Wait queue: 11367.
CONTEXT:  while updating tuple (0,2) in relation "foo"
STATEMENT:  UPDATE foo SET value = 3;

Most usefully, the new line is displayed by log entries due to
log_lock_waits, although of course it will be printed by any other log
message as well.

Author: Christian Kruse, some tweaks by Álvaro Herrera
Reviewed-by: Amit Kapila, Andres Freund, Tom Lane, Robert Haas

2014-03-19 15:10:36 -03:00

..

buffer

Fix capitalization in README.

2014-02-17 14:03:41 -05:00

file

C comments: remove odd blank lines after #ifdef WIN32 lines

2014-03-13 01:34:42 -04:00

freespace

Fix thinko in comment.

2014-02-07 10:28:06 +02:00

ipc

Rewrite comment for shm_mq_receive_bytes.

2014-03-18 11:53:28 -04:00

large_object

Update copyright for 2014

2014-01-07 16:05:30 -05:00

lmgr

Setup error context callback for transaction lock waits

2014-03-19 15:10:36 -03:00

page

Update copyright for 2014

2014-01-07 16:05:30 -05:00

smgr

Fix dangling smgr_owner pointer when a fake relcache entry is freed.

2014-03-07 13:28:52 +02:00

Makefile

Remove cvs keywords from all files.

2010-09-20 22:08:53 +02:00