Wal sender process not moving past wait_event_type: IO and wait_event: WALRead

Поиск
Список
Период
Сортировка
От Anurag Shrivastava
Тема Wal sender process not moving past wait_event_type: IO and wait_event: WALRead
Дата
Msg-id CADW1XLAuWyjnTo-B5YCGOwFzBM8FAsYzOocoU5xje0dWvmwOEw@mail.gmail.com
обсуждение исходный текст
Ответы Re: Wal sender process not moving past wait_event_type: IO and wait_event: WALRead  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Список pgsql-bugs
Дерево обсуждения

Hi Postgres team, 
We are facing an issue where we are unable to read data from a logical replication slot after a certain period of time. Every time after dropping the slot, it works fine for a few days and then again we are not able to read from the slot(we have been unable to find any queries that might be causing this issue). Each time the walsender process is getting stuck wait event type: IO and wait_event: WALRead. We've tried this with pgoutput, test_decoding and wal2json, with all three we have faced same issue.
Is there a way to be able to read the data from the same slot?

result for select * from pg_stat_activity:
datid
datname
pid
usesysid
usename
application_name
client_addr
client_hostname
client_port
backend_start
xact_start
query_start
state_change
wait_event_type
wait_event
state
backend_xid
backend_xmin
query
backend_type
16404
*******
115407
2354767601
*****
PostgreSQL JDBC Driver
<binary>
-
36322
1645710936593
-
-
1645710936941
IO
WALRead
active
-
-
-
walsender




1645710936593
-
-
1645710936941
IO
WALRead
active
-
-
-
walsender
--
Regards, 
Anurag Shrivastava,
Software Development Engineer, Hevo data

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: BUG #17416: Server crashes due to python3 stack overflow on executing multiple plpy.rollback() calls
Следующее
От: Tomas Vondra
Дата:
Сообщение: Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade