s3ext: fix abnormal behavior when QEs are reset
In some cases QEs may be reset, then S3 extension stays on undefined
behaviors. It may or may not catch the transaction abort signal.
For example, when GPDB cannot parse imported data from S3, query
and transaction are aborted and reset as new QE context starts.
To solve it, we keep the signal of transaction cancel once it is
captured until we stop all running threads and exit gracefully.
Signed-off-by: NHaozhou Wang <hawang@pivotal.io>
Showing
想要评论请 注册 或 登录