RDS for PostgreSQL wait events
The following table lists the wait events for RDS for PostgreSQL that most commonly indicate performance problems, and summarizes the most common causes and corrective actions..
Wait event | Definition |
---|---|
This event occurs when RDS for PostgreSQL is waiting to receive data from the client. |
|
This event occurs when RDS for PostgreSQL is waiting to write data to the client. |
|
This event occurs when a thread is active in CPU or is waiting for CPU. | |
These events occur when RDS for PostgreSQL creates temporary files. |
|
This event occurs when a connection waits on a backend process to read a required page from storage because the page isn't available in shared memory. |
|
IO:WALWrite | This event occurs when RDS for PostgreSQL is waiting for the write-ahead log
(WAL) buffers to be written to a WAL file.
|
This event occurs when a PostgreSQL application uses a lock to coordinate activity across multiple sessions. |
|
This event occurs when a backend process is waiting to lock a relation to extend it while another process has a lock on that relation for the same purpose. |
|
This event occurs when a query is waiting to acquire a lock on a table or view that's currently locked by another transaction. |
|
This event occurs when a transaction is waiting for a row-level lock. | |
This event occurs when a backend process is waiting to acquire a lock on a tuple. |
|
This event occurs when a session is waiting to associate a data block with a buffer in the shared buffer pool. |
|
This event occurs when RDS for PostgreSQL is waiting for other processes to finish their input/output (I/O) operations when concurrently trying to access a page. |
|
This event occurs when a session is waiting to read or write a data page in memory while another session has that page locked for writing. |
|
This event occurs when the RDS for PostgreSQL engine maintains the shared lock's memory area to allocate, check, and deallocate a lock when a fast path lock isn't possible. |
|
This event occurs when a server process has called the
|
|
This event indicates that the vacuum process is sleeping because the estimated cost limit has been reached. |