You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I observed something strange when processing all data from a huge table in a timeframe (1h) within that postgres executes auto vacuum/writes WAL. In my case this always occured short after another so I have not really pinpointed it WAL or auto vacuum.
However my fetch stream does then not continue delivering data, it remains in a blocked state.
postgres 16
Before going to deliver reproducible examples etc. I want to ask if this is a known problem or some other people have already tapped into?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I observed something strange when processing all data from a huge table in a timeframe (1h) within that postgres executes auto vacuum/writes WAL. In my case this always occured short after another so I have not really pinpointed it WAL or auto vacuum.
However my fetch stream does then not continue delivering data, it remains in a blocked state.
postgres 16
Before going to deliver reproducible examples etc. I want to ask if this is a known problem or some other people have already tapped into?
Beta Was this translation helpful? Give feedback.
All reactions