Lukas Fittl

See https://github.com/pganalyze/collector/pull/503 for an implementation that should work in the typical Kubernetes environment using fluentbit for log routing (tested with CloudNativePG, need to do a bit more testing with other...

@vishalsngl Sure - that is what the deparser is for. FWIW, it takes a bit of effort to walk the tree in Go currently, but technically anything is possible. For...

@vishalsngl Unfortunately I don't have the time available to provide more examples (we don't use the deparser with Go ourselves much currently, so coming up with examples is non-trivial). If...

@mpokryva Thanks for the report! It looks like we've omitted `constraints.sql` from the [list of filenames for the regression tests used by the deparser](https://github.com/pganalyze/libpg_query/blob/15-latest/test/deparse.c#L171), thus this wasn't noticed before. I...

@pyramation Yeah, unfortunately the RawStmt change was one in upstream Postgres with 10, so its not really something that can be avoided. For better or worse, Postgres parse trees are...

@pyramation Yeah, in general I would consider upgrading the parser version to be a major version increment on this library, and expect people to upgrade to that version whenever they...

@beeing Just one thought re: removing RawStmt.stmt for compatibility - I wouldn’t recommend this for two reasons: 1) That parse node sometimes has benefits (when parsing multiple statements it tells...

Yup, you got that right - typically you would have an `a_expr` in the WHERE clause if its a single expression, and a `bool_expr` if its multiple expressions. I don't...

> Thanks for pointing it out. But is there any other approach for this? Instead of having an additional quotes around the table_name? For other table_names, this works fine without...

@sinkog This is most likely a bug in [libpg_query](https://github.com/lfittl/libpg_query) (the underlying parser library) - do you mind opening an issue there so I have it on my radar?