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 have a question—in SqliteSaver, PostgresSaver, and their asynchronous versions, as far as I understand, you can not just fetch the last N messages directly, that would be optimized. So you either have to truncate or filter them yourself in State, which adds extra overhead. Has anyone ever considered this? How do you tackle it, or is it not really something to worry about?
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
Uh oh!
There was an error while loading. Please reload this page.
-
I have a question—in SqliteSaver, PostgresSaver, and their asynchronous versions, as far as I understand, you can not just fetch the last N messages directly, that would be optimized. So you either have to truncate or filter them yourself in State, which adds extra overhead. Has anyone ever considered this? How do you tackle it, or is it not really something to worry about?
Beta Was this translation helpful? Give feedback.
All reactions