| No |
Name |
Version |
Arguments |
Description |
| 1 |
lwlock-acquire |
8.2+ |
(int lockid, int mode) |
Probe that fires when an LWLock has been acquired. |
| 2 |
lwlock-release |
8.2+ |
(int lockid, int mode) |
Probe that fires when an LWLock has been released. |
| 3 |
lwlock-wait-start |
8.2+ |
(int lockid, int mode) |
Probe that fires when an LWLock was not immediately available and a backend has begun to wait for the lock to become available. Note the name change from 8.2. |
| 4 |
lwlock-wait-done |
8.2+ |
(int lockid, int mode) |
Probe that fires when a backend has been released from its wait for an LWLock. Note the name change from 8.2. |
| 5 |
lwlock-condacquire |
8.2+ |
(int lockid, int mode) |
Probe that fires when an LWLock was successfully acquired when the caller specified no waiting. |
| 6 |
lwlock-condacquire-fail |
8.2+ |
(int lockid, int mode) |
Probe that fires when an LWLock was not successfully acquired when the caller specified no waiting. |
| 7 |
lock-wait-start |
8.2+ |
(int locktag_field2, int lockmode) |
Probe that fires when a request for a heavyweight lock (lmgr lock) has begun to wait because the lock is not available. Note the name change from 8.2. |
| 8 |
lock-wait-done |
8.2+ |
(int locktag_field2, int lockmode) |
Probe that fires when a request for a heavyweight lock (lmgr lock) has finished waiting (i.e., has acquired the lock). Note the name change from 8.2. |
| 9 |
clog-checkpoint-start |
8.4 |
(bool) |
Probe that fires when the CLOG portion of the checkpoint is started. If arg0 is false, it is called during a postmaster shutdown. |
| 10 |
clog-checkpoint-done |
8.4 |
(bool) |
Probe that fires when the CLOG portion of the checkpoint is complete. If arg0 is false, it is called during a postmaster shutdown. |
| 11 |
subtrans-checkpoint-start |
8.4 |
(bool) |
Probe that fires when the SUBTRANS portion of the checkpoint is started. If arg0 is false, it is called during a postmaster shutdown. |
| 12 |
subtrans-checkpoint-done |
8.4 |
(bool) |
Probe that fires when the SUBTRANS portion of the checkpoint is complete. If arg0 is false, it is called during a postmaster shutdown. |
| 13 |
multixact-checkpoint-start |
8.4 |
(bool) |
Probe that fires when the MultiXact portion of the checkpoint is started. If arg0 is false, it is called during a postmaster shutdown. |
| 14 |
multixact-checkpoint-done |
8.4 |
(bool) |
Probe that fires when the MultiXact portion of the checkpoint is complete. If arg0 is false, it is called during a postmaster shutdown. |
| 15 |
buffer-checkpoint-start |
8.4 |
(int flags) |
Probe that fires when the shared buffers portion of the checkpoint is started. |
| 16 |
buffer-checkpoint-done |
8.4 |
() |
Probe that fires when the shared buffers portion of the checkpoint is complete. |
| 17 |
twophase-checkpoint-start |
8.4 |
() |
Probe that fires when the two-phase portion of the checkpoint is started. |
| 18 |
twophase-checkpoint-done |
8.4 |
() |
Probe that fires when the two-phase portion of the checkpoint is complete. |
| 19 |
buffer-sync-start |
8.4 |
(int, int) |
Probe that fires when all dirty shared buffers need to be synced to disk at checkpoint time. arg0 is the total number of buffers. arg1 is the number it intends to write. |
| 20 |
buffer-sync-done |
8.4 |
(int, int, int) |
Probe that fires when the buffer sync is complete. arg0 is the total number of buffers. arg1 is the number actually written. arg2 is the number it intended to write. |
| 21 |
buffer-sync-written |
8.4 |
(int) |
Probe that fires when the buffer pool syncing is in progress and a buffer has been successfully written. |
| 22 |
buffer-flush-start |
8.4 |
(Oid tablespace, Oid database, Oid relation) |
Probe that fires when the dirty blocks in the buffer pool are flushed to disk. This actually just passes the buffer contents to the kernel; the real write to disk happens later by the kernel. This is okay since the changes have already been written to the WAL. |
| 23 |
buffer-flush-done |
8.4 |
(Oid tablespace, Oid database, Oid relation) |
Probe that fires when the buffer flush is complete. |
| 24 |
buffer-read-start |
8.4 |
(BlockNumber blockNum, Oid tablespace, Oid database, Oid relation, bool isLocalBuf) |
Probe that fires when a buffer read is initiated |
| 25 |
buffer-read-done |
8.4 |
(BlockNumber blockNum, Oid tablespace, Oid database, Oid relation, bool isLocalBuf, bool isInBufPool) |
Probe that fires when a buffer read complete |
| 26 |
buffer-hit |
8.4 |
(bool isLocalBuf) |
Probe that fires when a read was satisfied from the buffer cache. If arg0 is true, buffer is local. |
| 27 |
buffer-miss |
8.4 |
(bool isLocalBuf) |
Probe that fires when a read has to go to disk. If arg0 is true, buffer is local. |
| 28 |
deadlock-found |
8.4 |
() |
Probe that fires when a deadlock is found by the deadlock detector |
| 29 |
sort-start |
8.4 |
(int, bool, int, int, bool) |
Probe that fires when sort is performed for tuple, index, and datum |
| 30 |
sort-done |
8.4 |
(unsigned long, long) |
Probe that fires when sort is complete |