postgres: stream Remote Queries COPY output to the Agent relay

[nubtron]

Stack

• Base: nubtron/remote-queries-poc
• This draft: production Postgres COPY-to-Agent relay bridge

Summary

• stream CSV COPY chunks synchronously through the native Agent callback
• enforce bounded backpressure and result-delivery caps
• return receipt-only metadata in upload mode
• keep Agent-owned credentials and intake routing out of Python
• preserve the ordinary small-result behavior when upload mode is omitted

Validation

• 129 focused tests passed
• lint passed
• independently reviewed

Deployment

Used only by the local Remote Queries intake proof setup; no shared deployment.

[datadog-datadog-prod-us1-2]

 

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 85.30%
• Overall Coverage: 93.95% (-0.28%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: bf9d874 | Docs | View more details | Give us feedback!}

[dd-octo-sts]

Validation Report

All 21 validations passed.

Show details

Validation	Description	Status
agent-reqs	Verify check versions match the Agent requirements file	✅
ci	Validate CI configuration and code coverage settings	✅
codeowners	Validate every integration has a CODEOWNERS entry	✅
config	Validate default configuration files against spec.yaml	✅
dep	Verify dependency pins are consistent and Agent-compatible	✅
http	Validate integrations use the HTTP wrapper correctly	✅
imports	Validate check imports do not use deprecated modules	✅
integration-style	Validate check code style conventions	✅
jmx-metrics	Validate JMX metrics definition files and config	✅
labeler	Validate PR labeler config matches integration directories	✅
legacy-signature	Validate no integration uses the legacy Agent check signature	✅
license-headers	Validate Python files have proper license headers	✅
licenses	Validate third-party license attribution list	✅
metadata	Validate metadata.csv metric definitions	✅
models	Validate configuration data models match spec.yaml	✅
openmetrics	Validate OpenMetrics integrations disable the metric limit	✅
package	Validate Python package metadata and naming	✅
qa-label	Validate the pull request declares whether it needs QA for the next Agent release	✅
readmes	Validate README files have required sections	✅
saved-views	Validate saved view JSON file structure and fields	✅
version	Validate version consistency between package and changelog	✅

View full run

[cit-pr-commenter-54b7da]

evalya-impact-summary

evalya impact analysis

Impact analysis: 0 selected, 0 skipped (of 0 test tasks)
Publish tasks:   1 (always emitted)
Diff (6 files):
  postgres/changelog.d/23499.added
  postgres/changelog.d/24311.added
  postgres/changelog.d/24311.fixed
  postgres/datadog_checks/postgres/remote_query.py
  postgres/tests/test_remote_query.py
  postgres/tests/test_remote_query_integration.py

Debug a specific task: evalya plan impact --path <path> --task <task>

Learn more about CI impact filtering

[nubtron]

Consolidated into #23499 (draft). The stack is linear, so #23499 fast-forwards to the hosted #24926 tree, preserving these commits. GitHub auto-merged this draft when the #23499 base advanced through the stack; the head branch has been restored and remains available for later explicit cleanup.