Lukas Fittl

Closing this for now since the integer constant issue was resolved separately, and the JSON duplication here seems best to keep here for now, to match `protobuf-cpp`.

> Hello, we use `libpg_query` via `pg_query_go`. We are interested in increasing the value of [NAMEDATALEN](https://github.com/pganalyze/libpg_query/blob/d49cc8e1ffe412d67d3dbae6c7020a35edacbe93/src/postgres/include/pg_config_manual.h#L22-L29) from its default value of 64. Can you share more about the use case...

Yeah, I agree it would be more logical to have this emitted in JSON with an explicit node like "Integer", instead of just the value. I tried to do a...

Thanks, makes sense! I do think we could reconsider what to do here, but will probably leave as-is for now since its not an urgent issue (rather an oddity). There...

> First of all, thanks for your gem! That's very useful. Glad to see you find it useful! > I developed some wrapper to pg_query to ease the parsing of...

You can leave the location field empty (causing it to be 0), or set it to -1 (which is what Postgres uses when the location is unknown). The location doesn't...

The error you're seeing in the collector logs appears to be related to a network problem, rather than something else - but its a bit hard to tell for sure....

Thanks for opening the issue as discussed & sharing the solution I've shared via email!

> Would you accept a PR to handle migrations_paths? Sure, I think that makes sense to support. Appreciate the report & your effort to fix it.

@fbriand-docto Thanks for reaching out! This was an intentional change in 2.2.0 to avoid data privacy-related issues with generated DO statements that contain personally identifiable information, such as produced by...