mirror of
https://github.com/neondatabase/neon.git
synced 2026-05-18 05:30:37 +00:00
walreceiver-after-ingest failpoint: use pausable_failpoint
Possibly the last commit was a red herring (still a good cleanup though). However, this one here is a definite executor stall at the failpoint. And it makes sense that it would cause the shutdown timeouts with the unified runtime, because the walreceiver code previously ran on a separate runtime.
This commit is contained in:
@@ -11,7 +11,6 @@ use std::{
|
||||
use anyhow::{anyhow, Context};
|
||||
use bytes::BytesMut;
|
||||
use chrono::{NaiveDateTime, Utc};
|
||||
use fail::fail_point;
|
||||
use futures::StreamExt;
|
||||
use postgres::{error::SqlState, SimpleQueryMessage, SimpleQueryRow};
|
||||
use postgres_ffi::WAL_SEGMENT_SIZE;
|
||||
@@ -326,7 +325,7 @@ pub(super) async fn handle_walreceiver_connection(
|
||||
filtered_records += 1;
|
||||
}
|
||||
|
||||
fail_point!("walreceiver-after-ingest");
|
||||
pausable_failpoint!("walreceiver-after-ingest");
|
||||
|
||||
last_rec_lsn = lsn;
|
||||
|
||||
|
||||
Reference in New Issue
Block a user