Lukas Fittl
Lukas Fittl
Hi @hdlinh1808! In order to remove the redundant NOT you would have to modify the parse tree so that the relevant parts are no longer present (I'd suggest comparing with...
> Hi @lfittl , how to deserialise a JSON string into a GO struct to traverse the Tree returned by `ParsePlPgSqlToJSON()` ? There is currently no built-in mechanism for that,...
> What are our thoughts about modifying the collector logic to handle multiple system snapshots at once to use fewer AWS API calls? I think overall this would make sense...
Yeah, that's probably because of the amount of parse nodes you get with a statement like that - the CPU pinning is probably just because of the amount of cycles...
> Any update on this? We're going to have to migrate to a different parser. Its not clear what the root cause is, and I'm not sure how to debug...
@sanyamsinghal @priyanshi-yb @h3n4l This has been released now in v6.1.0 - thanks for your patience.
@skcuslleb There is no helper that gets the target list column names today - but certainly open to adding one, similar to filter columns. A PR to discuss further would...
Closing this since the mentioned PR #256 was merged.
I think the problem here is that `user` is a keyword (see https://www.postgresql.org/docs/current/sql-keywords-appendix.html), and so you need to escape it like this: `"user"` (in Postgres syntax,`"` is used to escape...
@owst Thanks for the contribution! Looks like we do also need to bump up `protobuf` (at least a bit) to get this to work? (see failing CI)