Lukas Fittl

> @lfittl Did you get a chance to take a look at this PR? Not yet! I saw this come in, but had some competing priorities. This is on my...

This has been implemented in https://github.com/pganalyze/collector/pull/747 (rebase of https://github.com/pganalyze/collector/pull/711 authored by @rauanmayemir) and released in pganalyze collector release 0.67.0 released today. Thanks everyone for your patience in getting this resolved...

> We actually changed from DD to Grafana. Is integration with the PgAnalyze OTEL exporter and Grafana supported? Looks like I repeated my mistake in not responding to you on...

This is likely caused by a query that has a deeply nested syntax tree. If the protobuf version is sufficiently new, the limit should be 1000 entries deep ([see source](https://github.com/pganalyze/pg_query/blob/d8a6b8f2028978c3e9295b4129060fd808bd6989/lib/pg_query/parse.rb#L9)),...

@david-h-muller Closing this since your PR (#268) addressed this, and has been released in [17-6.2.0](https://github.com/pganalyze/libpg_query/releases/tag/17-6.2.0).

Could it be that you don't have cgo support enabled? The main file has a cgo build tag (https://github.com/pganalyze/pg_query_go/blob/main/pg_query.go#L2), so without cgo it would give you an import error like...

This is due to how Postgres handles certain queries inside PL/pgSQL functions, i.e. they are their own parsing cycle, rather than handled by the PL/pgSQL parser. There is no mechanism...

@dependabot rebase

@dependabot rebase

Thanks for opening an issue on this! You're correct that we're not exposing this today, but I don't think there is a good reason for it - we just didn't...