Gajus Kuizinas

@everesio Do you mind closing this in favor of https://github.com/temporalio/helm-charts/pull/281? Just to reduce uncertainty about getting either of these PRs out

Annoying that this is something that would take Temporal team a minute to setup, meanwhile forces everyone else to spend days searching for workarounds.

Here is a step by step guide on how to do it: https://joao.neto.pt/posts/2022/github-helm-registry/

Seriously, save yourself time and write your own Helm chart. Took me one afternoon, ... while before this I've spent weeks debugging issues with Temporal provided Helm chart.

Having looked at the source code, `pg-query-stream` is a wrapper around `pg-cursor`. Meanwhile, `pg-cursor` does have access to result object. It could be implemented simply as: ```diff _read (size) {...

As a quick workaround, I have inlined pg-query-stream. This is the solution that I have used: https://github.com/gajus/slonik/commit/fce4d220f2bf22b9d13a08769ae987e45dfdb2b6 As suggested in this issue, each date event emits row and fields data.

@dgozman @pavelfeldman @aslushnikov is this on anyone's radar?

@mattjennings Have you managed to figure a workaround of any kind?

Unfortunately, the underlying library that supports it does not appear to quite work https://github.com/DataDog/import-in-the-middle/issues/58

I believe this to be related https://github.com/open-telemetry/opentelemetry-js/issues/4437