Maciek Sakrejda

This was addressed with [CONFIG_CONTENTS](https://github.com/pganalyze/collector/blob/main/CHANGELOG.md#0452------2022-08-31) in v0.45.2.

@JordanP can you tell us more about the nature of the different workloads (and log output)? Are the two lines in the graph you pasted above for the two different...

Hi @dbamohsin -- could you try with the 0.36 we just released when you have a chance? I don't think any of the fixes there would have impacted memory usage...

Hi Joe, As Lukas mentioned offline, this makes sense in general. In some ways this is similar to https://github.com/pganalyze/collector/pull/62 . And it would not require any server-side changes assuming that...

Regarding the refactoring, my gut feeling is that if we go with the separate mapping step, that's probably easier as a shared helper function rather than a first-class type for...

:+1:, a good use case for this is handling elements like react-router's Link that wrap anchor tags.

Actually, because Link just renders an anchor, that's mostly moot here. But here's a different use case: menu items could be used to trigger form submission (e.g., see the log...

Oh good point, I could work with ReturnType, yeah. I think it'd still be nice to have something more straightforward (especially if as you say this will get more complex...

This is also potentially an issue with Kafka itself, right? If the message exceeds Kafka's `messages.max.bytes`, there's not much bottledwater can do here... /cc @samstokes

Another possible (long-term--definitely don't think this is worth doing short-term) solution is to break up the value into separate smaller messages that fit under the limit. This is pretty ugly...