diff options
| author | Amit Kapila <akapila@postgresql.org> | 2023-02-07 09:58:19 +0530 |
|---|---|---|
| committer | Amit Kapila <akapila@postgresql.org> | 2023-02-07 09:58:19 +0530 |
| commit | d9d7fe68d35e1e10c7c8276d07f5abf9c477cb13 (patch) | |
| tree | 45a577ac285d25cd18d993942bf562fbb2945f7b /src/backend/access/gist/gistproc.c | |
| parent | cfcf56f92398c2827fcca9406e7c7ea6caab83c2 (diff) | |
| download | postgresql-d9d7fe68d35e1e10c7c8276d07f5abf9c477cb13.tar.gz | |
Use appropriate wait event when sending data in the apply worker.
Currently, we reuse WAIT_EVENT_LOGICAL_PARALLEL_APPLY_STATE_CHANGE in the
apply worker while sending data to the parallel apply worker via a shared
memory queue. This is not appropriate as one won't be able to distinguish
whether the worker is waiting for sending data or for the state change.
To patch instead uses the wait event WAIT_EVENT_MQ_SEND which has been
already used in blocking mode while sending data via a shared memory
queue.
Author: Hou Zhijie
Reviewed-by: Kuroda Hayato, Amit Kapila
Discussion: https://postgr.es/m/OS0PR01MB57161C680B22E4C591628EE994DA9@OS0PR01MB5716.jpnprd01.prod.outlook.com
Diffstat (limited to 'src/backend/access/gist/gistproc.c')
0 files changed, 0 insertions, 0 deletions