feat(node): Add ignoreConnectSpans option to postgresIntegration

[Lms24]

OTel's PgInstrumentation exposes an option to ignore pg(.pool).connect spans.
This option was added recently in open-telemetry/opentelemetry-js-contrib#3280. We should allow users to configure our wrapping postgresIntegration with the same option.

Usage:

Sentry.init({
  dsn: '...',
  tracesSampleRate: 1.0,
  integrations: [Sentry.postgresIntegration({ ignoreConnectSpans: true })],
});

Side product of looking into #19290 which turned out not to be an SDK issue . But this reminded me that we had #16536 open which we should tackle at some point. So I figured, why not now.

Docs PR: getsentry/sentry-docs#16358

closes #16536

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[github-actions]

Codecov Results 📊

---

Generated by Codecov Action

[github-actions]

size-limit report 📦

Path	Size	% Change	Change
@sentry/browser	25.56 kB	-	-
@sentry/browser - with treeshaking flags	24.08 kB	-	-
@sentry/browser (incl. Tracing)	42.36 kB	-	-
@sentry/browser (incl. Tracing, Profiling)	47.03 kB	-	-
@sentry/browser (incl. Tracing, Replay)	81.18 kB	-	-
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	70.8 kB	-	-
@sentry/browser (incl. Tracing, Replay with Canvas)	85.87 kB	-	-
@sentry/browser (incl. Tracing, Replay, Feedback)	98.03 kB	-	-
@sentry/browser (incl. Feedback)	42.29 kB	-	-
@sentry/browser (incl. sendFeedback)	30.23 kB	-	-
@sentry/browser (incl. FeedbackAsync)	35.22 kB	-	-
@sentry/browser (incl. Metrics)	26.74 kB	-	-
@sentry/browser (incl. Logs)	26.88 kB	-	-
@sentry/browser (incl. Metrics & Logs)	27.56 kB	-	-
@sentry/react	27.33 kB	-	-
@sentry/react (incl. Tracing)	44.72 kB	-	-
@sentry/vue	30.01 kB	-	-
@sentry/vue (incl. Tracing)	44.21 kB	-	-
@sentry/svelte	25.58 kB	-	-
CDN Bundle	28.11 kB	-	-
CDN Bundle (incl. Tracing)	43.2 kB	-	-
CDN Bundle (incl. Logs, Metrics)	28.95 kB	-	-
CDN Bundle (incl. Tracing, Logs, Metrics)	44.03 kB	-	-
CDN Bundle (incl. Replay, Logs, Metrics)	68.02 kB	-	-
CDN Bundle (incl. Tracing, Replay)	80.07 kB	-	-
CDN Bundle (incl. Tracing, Replay, Logs, Metrics)	80.94 kB	-	-
CDN Bundle (incl. Tracing, Replay, Feedback)	85.5 kB	-	-
CDN Bundle (incl. Tracing, Replay, Feedback, Logs, Metrics)	86.4 kB	-	-
CDN Bundle - uncompressed	82.22 kB	-	-
CDN Bundle (incl. Tracing) - uncompressed	127.93 kB	-	-
CDN Bundle (incl. Logs, Metrics) - uncompressed	85.05 kB	-	-
CDN Bundle (incl. Tracing, Logs, Metrics) - uncompressed	130.76 kB	-	-
CDN Bundle (incl. Replay, Logs, Metrics) - uncompressed	208.71 kB	-	-
CDN Bundle (incl. Tracing, Replay) - uncompressed	244.81 kB	-	-
CDN Bundle (incl. Tracing, Replay, Logs, Metrics) - uncompressed	247.63 kB	-	-
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	257.61 kB	-	-
CDN Bundle (incl. Tracing, Replay, Feedback, Logs, Metrics) - uncompressed	260.42 kB	-	-
@sentry/nextjs (client)	47.04 kB	-	-
@sentry/sveltekit (client)	42.81 kB	-	-
@sentry/node-core	52.15 kB	-	-
@sentry/node	166.53 kB	+0.02%	+22 B 🔺
@sentry/node - without tracing	93.95 kB	-	-
@sentry/aws-serverless	109.45 kB	-0.01%	-1 B 🔽

View base workflow run

[github-actions]

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	8,813	-	9,512	-7%
GET With Sentry	1,595	18%	1,616	-1%
GET With Sentry (error only)	5,984	68%	6,033	-1%
POST Baseline	1,107	-	1,197	-8%
POST With Sentry	547	49%	590	-7%
POST With Sentry (error only)	963	87%	1,051	-8%
MYSQL Baseline	3,240	-	3,335	-3%
MYSQL With Sentry	428	13%	464	-8%
MYSQL With Sentry (error only)	2,633	81%	2,689	-2%

View base workflow run

[RulaKhaled]

lgtm