diagnostic-channel-publishers to support PgQueryStream about node-diagnostic-channel

[imzacm]

I've got this same issue with pg-cursor, I would appreciate either a fix, or if someone can tell me to disable the pg patching (but keep all other functionality).

I forgot to say, I'm using applicationinsights 1.8.5, I've had no problems up to today when I've updated all of my dependencies, when that failed I reinstalled the old deps and got the same issue, so not sure if a dependency somewhere upstream has changed, but the issue seems to stem from here (please correct me if I'm wrong).

Edit:
I've found a temporary solution,
Installing pg under a different name (pg-dup), and using this when I want to use a cursor:

// const { Pool } = require('pg')
const { Pool } = require('pg-dup')
const Cursor = require('pg-cursor')

My package.json dependencies:

"pg": "8.3.0",
"pg-cursor": "2.3.0",
"pg-dup": "npm:[email protected]"

[imzacm]

Thank you, I couldn't see that documented anywhere.
Is there any plan to add support for pg-cursor? Or will I have to permanently disable patching pg?

Either way I'm glad I've got a solution, it'll just be good to know :)

[luciferankon]

Hi is there any updates to this? We have intermittently turned off the patching but that's causing our pg logs also not showing up in the App insights. Is there a Permanent solution planned? @markwolff I see the PR is also not merged yet.

[markwolff]

You can disable patching for a module via environment variable

APPLICATION_INSIGHTS_NO_PATCH_MODULES=pg