Home / multigres / multigres
AI Slop Code RIsk Monitor

multigres/multigres

Vitess for Postgres

4.9 Low pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for multigres/multigres, a Go project with 2,668 GitHub stars. SynthScan examined 775,692 lines of code across 2086 source files, recording 3404 pattern matches distributed across 13 syntactic categories. The legacy adjusted pattern signal is 4.9 (Low pattern signal); it is not an authorship estimate.

Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.

4.9
Adjusted Signal
4.9
Raw Pattern Score
100%
Time Factor
2026-10-09
Last Push
2.7K
Stars
Go
Language
775.7K
Lines of Code
2.1K
Files
3.4K
Pattern Hits
2026-10-12
Scan Date
0.00
HC Hit Rate

Risk Review · v3

Use each vector to guide manual verification of the underlying findings.

Cognitive Ownership Risk 20.6/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 3350 finding(s).

Hallucinated Dependency & Supply Chain Risk 0.1/100 · LOW

Are imports declared and package/API names verified? 11 finding(s).

Agent Over-Engineering Ratio 1.1/100 · LOW

Are wrappers, guards, and repeated structures necessary? 47 finding(s).

PR Review Velocity Impact 20.5/100 · LOW

Which changes need focused human review? 3404 finding(s).

What These Metrics Mean

Adjusted Signal
Legacy pattern score normalized per 1,000 scanned lines and multiplied by the repository-level time factor. It is not an estimate of AI authorship.
Raw Pattern Score
Sum of severity- and context-weighted pattern findings before applying the time factor.
Time Factor
A coarse multiplier based on repository last-push metadata. It does not identify when individual code was written.
Pattern Hits
Count of configured pattern findings. Review each location and surrounding code before acting.
HC Hit Rate
High- and critical-severity findings per scanned file. Severity is a configured detector weight, not proof of a vulnerability or authorship.
Lines / Files
Scan coverage denominators used by the legacy normalized score.

Pattern-Signal History

This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.

Severity Breakdown

Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.

CRITICAL 0HIGH 0MEDIUM 77LOW 3327

Directory Score Breakdown

This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.

Pattern Findings

The scanner identified 3404 distinct pattern matches across 13 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.

Reading the findings table: The Severity column indicates the configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.

Over-Commented Block3042 hits · 3000 pts
SeverityFileLineSnippetContext
LOWcodecov.yml21 # so coverage-collecting CI never executes any of it — every new lineCOMMENT
LOW.golangci.yml1# Copyright 2025 Supabase, Inc.COMMENT
LOW.golangci.yml181 desc: "Please use math/rand/v2"COMMENT
LOW.golangci.yml221 # Check for locks erroneously passed by value.COMMENT
LOW.golangci.yml241 # Check for mistakes using HTTP responses.COMMENT
LOWdocker-compose.yml1# All-in-one Multigres cluster for local development and CI compatibilityCOMMENT
LOWdocker-compose.yml21 # bundles the required extensions + pgBackRest and setCOMMENT
LOWdocker-compose.yml41 # AtLeastN(2) durability policy, so a single pooler can never elect aCOMMENT
LOWdemo/k8s/port-forward-infra.sh1#!/usr/bin/env bashCOMMENT
LOWdemo/k8s/update-grafana-dashboard.sh1#!/usr/bin/env bashCOMMENT
LOWdemo/k8s/backup-restore.sh1#!/bin/bashCOMMENT
LOWdemo/k8s/backup-restore.sh21# - kubectl configured to access the clusterCOMMENT
LOWdemo/k8s/k8s-multipooler-statefulset.yaml1# We're trying to see if Statefullsets can be made to work.COMMENT
LOWdemo/k8s/launch-multigres-cluster.sh1#!/usr/bin/env zshCOMMENT
LOWdemo/k8s/launch-infra.sh1#!/usr/bin/env zshCOMMENT
LOWdemo/k8s/teardown.sh1#!/usr/bin/env zshCOMMENT
LOWdemo/k8s/start-qs.sh1#!/bin/bashCOMMENT
LOWdemo/k8s/failover-test.go1// Copyright 2025 Supabase, Inc.COMMENT
LOWdemo/k8s/port-forward-multigres-cluster.sh1#!/usr/bin/env bashCOMMENT
LOWdemo/k8s/k8s-postgres-password-secret.yaml1# Example Secret holding the PostgreSQL superuser password. Each multipoolerCOMMENT
LOWdemo/observability/sampling-config.yaml1# OpenTelemetry Sampling Configuration for Multigres kind_demoCOMMENT
LOWdemo/local/failover-test.go1// Copyright 2025 Supabase, Inc.COMMENT
LOWtools/setup_s3_cluster.sh1#!/bin/bashCOMMENT
LOWtools/download_tool.sh1#!/bin/bashCOMMENT
LOWtools/safe_download.sh1#!/bin/bashCOMMENT
LOWtools/naming_linter.sh1#!/bin/bashCOMMENT
LOWtools/naming_linter.sh21# "MultiGateway", "MultiAdmin", etc. (and their leading-lowercase variantsCOMMENT
LOWtools/setup_build_tools.sh1#!/bin/bashCOMMENT
LOWtools/setup_build_tools.sh481# symlink the resulting binary into $MTROOT/bin/pgproto.COMMENT
LOWtools/tool_checksums.sh1#!/bin/bashCOMMENT
LOWtools/run_super_linter.sh1#!/bin/bashCOMMENT
LOWtools/openapi/lint/main.go1// Copyright 2026 Supabase, Inc.COMMENT
LOWtools/openapi/lint/main_test.go1// Copyright 2026 Supabase, Inc.COMMENT
LOWtools/openapi/normalize/main.go1// Copyright 2026 Supabase, Inc.COMMENT
LOWtools/openapi/normalize/main_test.go1// Copyright 2026 Supabase, Inc.COMMENT
LOWdocker/pgregress-generate.sh1#!/usr/bin/env bashCOMMENT
LOWdocker/pgregress-generate.sh21#COMMENT
LOWdocker/cluster-entrypoint.sh1#!/usr/bin/env bashCOMMENT
LOWdocker/cluster-entrypoint.sh21set -euo pipefailCOMMENT
LOWdocker/cluster-entrypoint.sh41COMMENT
LOWdocker/cluster-entrypoint.sh61# Connections held back from the pooler when MULTIGRES_PG_MAX_CONNECTIONS is set.COMMENT
LOWgo/cmd/minigres/plugin_topo.go1// Copyright 2026 Supabase, Inc.COMMENT
LOWgo/cmd/minigres/main.go1// Copyright 2026 Supabase, Inc.COMMENT
LOWgo/cmd/minigres/main_test.go1// Copyright 2026 Supabase, Inc.COMMENT
LOWgo/cmd/multigateway/plugin_topo.go1// Copyright 2025 Supabase, Inc.COMMENT
LOWgo/cmd/multigateway/main.go1// Copyright 2025 Supabase, Inc.COMMENT
LOWgo/cmd/multigateway/main_test.go1// Copyright 2025 Supabase, Inc.COMMENT
LOWgo/cmd/multiadmin/plugin_topo.go1// Copyright 2025 Supabase, Inc.COMMENT
LOWgo/cmd/multiadmin/main.go1// Copyright 2025 Supabase, Inc.COMMENT
LOWgo/cmd/multiadmin/main_test.go1// Copyright 2025 Supabase, Inc.COMMENT
LOWgo/cmd/pgctld/main.go1// Copyright 2025 Supabase, Inc.COMMENT
LOWgo/cmd/pgctld/command/reload.go1// Copyright 2025 Supabase, Inc.COMMENT
LOWgo/cmd/pgctld/command/start_test.go1// Copyright 2025 Supabase, Inc.COMMENT
LOWgo/cmd/pgctld/command/flags_test.go1// Copyright 2026 Supabase, Inc.COMMENT
LOWgo/cmd/pgctld/command/version.go1// Copyright 2025 Supabase, Inc.COMMENT
LOWgo/cmd/pgctld/command/server.go1// Copyright 2025 Supabase, Inc.COMMENT
LOWgo/cmd/pgctld/command/server.go601 // that is up — or still starting after a Start whose success was misreportedCOMMENT
LOWgo/cmd/pgctld/command/metrics.go1// Copyright 2026 Supabase, Inc.COMMENT
LOWgo/cmd/pgctld/command/pg_instance_test.go1// Copyright 2026 Supabase, Inc.COMMENT
LOWgo/cmd/pgctld/command/init_secrets_test.go1// Copyright 2026 Supabase, Inc.COMMENT
2982 more matches not shown…
Structural Annotation Overuse123 hits · 221 pts
SeverityFileLineSnippetContext
LOW⚡go/cmd/pgctld/command/server_test.go824 // Step 1: Simulate a running postgres by installing a postmaster.pid thatCOMMENT
LOW⚡go/cmd/pgctld/command/server_test.go829 // Step 2: Stop postgres. This is the first part of the stop→rewind→start sequence.COMMENT
LOW⚡go/cmd/pgctld/command/server_test.go834 // Step 3: Run pg_rewind (dry-run). The service must accept this call after a stop;COMMENT
LOW⚡go/cmd/pgctld/command/server_test.go844 // Step 4: Start postgres again as standby. This is the critical step: the serviceCOMMENT
LOWgo/test/s3mock/test-pgbackrest.sh79# Step 1: Build and start S3 mock serverCOMMENT
LOWgo/test/s3mock/test-pgbackrest.sh107# Step 2: Initialize PostgreSQL clusterCOMMENT
LOWgo/test/s3mock/test-pgbackrest.sh141# Step 3: Configure pgBackRestCOMMENT
LOWgo/test/s3mock/test-pgbackrest.sh174# Step 4: Create pgBackRest stanzaCOMMENT
LOWgo/test/s3mock/test-pgbackrest.sh190# Step 5: Create full backupCOMMENT
LOW⚡go/test/s3mock/test-pgbackrest.sh220# Step 6: Extract backup label from info outputCOMMENT
LOW⚡go/test/s3mock/test-pgbackrest.sh230# Step 7: Verify backup integrityCOMMENT
LOW⚡go/test/s3mock/test-pgbackrest.sh239# Step 8: Test restoreCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go82 // Step 2: Initialize data directoryCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go86 // Step 3: Start PostgreSQLCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go91 // Step 4: Check status - should be running, with the adoptable configCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go107 // Step 5: Get versionCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go112 // Step 6: Reload configCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go117 // Step 7: RestartCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go122 // Step 8: Check status againCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go127 // Step 9: Stop PostgreSQLCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go132 // Step 10: Final status checkCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go379 // Step 1: Check initial status - should be NOT_INITIALIZEDCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go385 // Step 2: Try to start without initialization - should fail with proper errorCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go391 // Step 3: Try to stop without initialization - should return appropriate messageCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go401 // Step 4: Try restart without initialization - should failCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go406 // Step 5: Try reload config without initialization - should failCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go411 // Step 6: Initialize should workCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go416 // Step 7: Status should now show STOPPEDCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go70 // Step 1: Check initial status. Config-level fields (pooler dir, host)COMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_test.go106 // Step 2: Check status - should show stopped after initCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_test.go116 // Step 3: Test help commands workCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_test.go122 // Step 4: Test that real PostgreSQL binaries are detectedCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_test.go129 // Step 5: Test initialization works with real PostgreSQLCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_test.go1197 // Step 1: Initialize the database firstCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_test.go1206 // Step 2: Check status - should be stopped after initCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_test.go1216 // Step 3: Start PostgreSQLCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_test.go1222 // Step 4: Check status - should be runningCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_test.go1229 // Step 5: Reload configurationCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_test.go1235 // Step 6: Restart PostgreSQLCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_test.go1241 // Step 7: Check status again - should still be runningCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_test.go1248 // Step 8: Stop PostgreSQLCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_test.go1254 // Step 9: Final status check - should be stoppedCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_test.go85 // Step 1: Initialize the database firstCOMMENT
LOW…/endtoend/localprovisioner/refresh_credentials_test.go101 // Step 1: Initialize cluster with S3 + UseEnvCredentialsCOMMENT
LOW…/endtoend/localprovisioner/refresh_credentials_test.go123 // Step 2: Verify initial credentials file existsCOMMENT
LOW…/endtoend/localprovisioner/refresh_credentials_test.go150 // Step 3: Change AWS credentials in environmentCOMMENT
LOW…/endtoend/localprovisioner/refresh_credentials_test.go162 // Step 4: Run refresh-credentials commandCOMMENT
LOW…/endtoend/localprovisioner/refresh_credentials_test.go178 // Step 5: Verify credentials file updated with new valuesCOMMENT
LOW…/endtoend/localprovisioner/refresh_credentials_test.go202 // Step 6: Verify file permissions preserved (0600)COMMENT
LOW⚡go/test/endtoend/multiorch/demote_stale_primary_test.go98 // Step 1: Kill postgres on primary to trigger failoverCOMMENT
LOW⚡go/test/endtoend/multiorch/demote_stale_primary_test.go102 // Step 2: Wait for new primary electionCOMMENT
LOW⚡go/test/endtoend/multiorch/demote_stale_primary_test.go108 // Step 3: Write data to new primary to ensure timeline has divergedCOMMENT
LOW⚡go/test/endtoend/multiorch/demote_stale_primary_test.go112 // Step 4: Re-enable postgres auto-restarts on the old primary. The newCOMMENT
LOW⚡go/test/endtoend/multiorch/demote_stale_primary_test.go120 // Step 5: Wait for multiorch to detect and repair divergence. Once postgresCOMMENT
LOW⚡go/test/endtoend/multiorch/demote_stale_primary_test.go127 // Step 6: Verify old primary is now replicating from new primaryCOMMENT
LOW⚡go/test/endtoend/multiorch/demote_stale_primary_test.go131 // Step 7: Verify replication is actually working by writing data and checking it replicatesCOMMENT
LOW⚡go/test/endtoend/multiorch/demote_stale_primary_test.go135 // Step 8: Verify the old primary was demoted via SetPrimary.COMMENT
LOW⚡go/test/endtoend/multiorch/demote_stale_primary_test.go140 // Step 9: Verify consensus.recruit event was emitted during failover.COMMENT
LOW⚡go/test/endtoend/multiorch/demote_stale_primary_test.go196 // Step 1: Gracefully shutdown postgres on primary to trigger failover.COMMENT
LOW⚡go/test/endtoend/multiorch/demote_stale_primary_test.go204 // Step 2: Wait for new primary electionCOMMENT
63 more matches not shown…
Verbosity Indicators111 hits · 204 pts
SeverityFileLineSnippetContext
LOW⚡go/cmd/pgctld/command/server_test.go824 // Step 1: Simulate a running postgres by installing a postmaster.pid thatCOMMENT
LOW⚡go/cmd/pgctld/command/server_test.go829 // Step 2: Stop postgres. This is the first part of the stop→rewind→start sequence.COMMENT
LOW⚡go/cmd/pgctld/command/server_test.go834 // Step 3: Run pg_rewind (dry-run). The service must accept this call after a stop;COMMENT
LOW⚡go/cmd/pgctld/command/server_test.go844 // Step 4: Start postgres again as standby. This is the critical step: the serviceCOMMENT
LOWgo/test/s3mock/test-pgbackrest.sh79# Step 1: Build and start S3 mock serverCOMMENT
LOWgo/test/s3mock/test-pgbackrest.sh107# Step 2: Initialize PostgreSQL clusterCOMMENT
LOWgo/test/s3mock/test-pgbackrest.sh141# Step 3: Configure pgBackRestCOMMENT
LOWgo/test/s3mock/test-pgbackrest.sh174# Step 4: Create pgBackRest stanzaCOMMENT
LOWgo/test/s3mock/test-pgbackrest.sh190# Step 5: Create full backupCOMMENT
LOW⚡go/test/s3mock/test-pgbackrest.sh220# Step 6: Extract backup label from info outputCOMMENT
LOW⚡go/test/s3mock/test-pgbackrest.sh230# Step 7: Verify backup integrityCOMMENT
LOW⚡go/test/s3mock/test-pgbackrest.sh239# Step 8: Test restoreCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go82 // Step 2: Initialize data directoryCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go86 // Step 3: Start PostgreSQLCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go91 // Step 4: Check status - should be running, with the adoptable configCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go107 // Step 5: Get versionCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go112 // Step 6: Reload configCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go117 // Step 7: RestartCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go122 // Step 8: Check status againCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go127 // Step 9: Stop PostgreSQLCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go132 // Step 10: Final status checkCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go379 // Step 1: Check initial status - should be NOT_INITIALIZEDCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go385 // Step 2: Try to start without initialization - should fail with proper errorCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go391 // Step 3: Try to stop without initialization - should return appropriate messageCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go401 // Step 4: Try restart without initialization - should failCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go406 // Step 5: Try reload config without initialization - should failCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go411 // Step 6: Initialize should workCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_grpc_test.go416 // Step 7: Status should now show STOPPEDCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go70 // Step 1: Check initial status. Config-level fields (pooler dir, host)COMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_test.go106 // Step 2: Check status - should show stopped after initCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_test.go116 // Step 3: Test help commands workCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_test.go122 // Step 4: Test that real PostgreSQL binaries are detectedCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_test.go129 // Step 5: Test initialization works with real PostgreSQLCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_test.go1197 // Step 1: Initialize the database firstCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_test.go1206 // Step 2: Check status - should be stopped after initCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_test.go1216 // Step 3: Start PostgreSQLCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_test.go1222 // Step 4: Check status - should be runningCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_test.go1229 // Step 5: Reload configurationCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_test.go1235 // Step 6: Restart PostgreSQLCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_test.go1241 // Step 7: Check status again - should still be runningCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_test.go1248 // Step 8: Stop PostgreSQLCOMMENT
LOW⚡go/test/endtoend/pgctld/pgctld_test.go1254 // Step 9: Final status check - should be stoppedCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_test.go85 // Step 1: Initialize the database firstCOMMENT
LOW…/endtoend/localprovisioner/refresh_credentials_test.go101 // Step 1: Initialize cluster with S3 + UseEnvCredentialsCOMMENT
LOW…/endtoend/localprovisioner/refresh_credentials_test.go123 // Step 2: Verify initial credentials file existsCOMMENT
LOW…/endtoend/localprovisioner/refresh_credentials_test.go150 // Step 3: Change AWS credentials in environmentCOMMENT
LOW…/endtoend/localprovisioner/refresh_credentials_test.go162 // Step 4: Run refresh-credentials commandCOMMENT
LOW…/endtoend/localprovisioner/refresh_credentials_test.go178 // Step 5: Verify credentials file updated with new valuesCOMMENT
LOW…/endtoend/localprovisioner/refresh_credentials_test.go202 // Step 6: Verify file permissions preserved (0600)COMMENT
LOW⚡go/test/endtoend/multiorch/demote_stale_primary_test.go98 // Step 1: Kill postgres on primary to trigger failoverCOMMENT
LOW⚡go/test/endtoend/multiorch/demote_stale_primary_test.go102 // Step 2: Wait for new primary electionCOMMENT
LOW⚡go/test/endtoend/multiorch/demote_stale_primary_test.go108 // Step 3: Write data to new primary to ensure timeline has divergedCOMMENT
LOW⚡go/test/endtoend/multiorch/demote_stale_primary_test.go112 // Step 4: Re-enable postgres auto-restarts on the old primary. The newCOMMENT
LOW⚡go/test/endtoend/multiorch/demote_stale_primary_test.go120 // Step 5: Wait for multiorch to detect and repair divergence. Once postgresCOMMENT
LOW⚡go/test/endtoend/multiorch/demote_stale_primary_test.go127 // Step 6: Verify old primary is now replicating from new primaryCOMMENT
LOW⚡go/test/endtoend/multiorch/demote_stale_primary_test.go131 // Step 7: Verify replication is actually working by writing data and checking it replicatesCOMMENT
LOW⚡go/test/endtoend/multiorch/demote_stale_primary_test.go135 // Step 8: Verify the old primary was demoted via SetPrimary.COMMENT
LOW⚡go/test/endtoend/multiorch/demote_stale_primary_test.go140 // Step 9: Verify consensus.recruit event was emitted during failover.COMMENT
LOW⚡go/test/endtoend/multiorch/demote_stale_primary_test.go196 // Step 1: Gracefully shutdown postgres on primary to trigger failover.COMMENT
LOW⚡go/test/endtoend/multiorch/demote_stale_primary_test.go204 // Step 2: Wait for new primary electionCOMMENT
51 more matches not shown…
Decorative Section Separators42 hits · 164 pts
SeverityFileLineSnippetContext
MEDIUMdemo/k8s/k8s-multipooler-statefulset.yaml11 # ===================================================COMMENT
MEDIUM⚡…t/endtoend/queryserving/postgresttests/io_selection.go52 // ── Role settings hoisted per request ───────────────────────────────────COMMENT
MEDIUM⚡…t/endtoend/queryserving/postgresttests/io_selection.go58 // ── Function / hoisted-transaction settings ─────────────────────────────COMMENT
MEDIUM⚡…t/endtoend/queryserving/postgresttests/io_selection.go66 // ── Superuser-granted role settings (GRANT SET ON PARAMETER) ─────────────COMMENT
MEDIUM⚡…t/endtoend/queryserving/postgresttests/io_selection.go70 // ── Prepared statements through the pooler ──────────────────────────────COMMENT
MEDIUM⚡…t/endtoend/queryserving/postgresttests/io_selection.go73 // ── LISTEN/NOTIFY-triggered config & schema reload ──────────────────────COMMENT
MEDIUMgo/common/consensus/proposals_test.go240 // ── outgoing cohort mode ──────────────────────────────────────────────────COMMENT
MEDIUMgo/common/consensus/proposals_test.go1039 // ── incoming cohort mode (bootstrap) ─────────────────────────────────────COMMENT
MEDIUMgo/common/sqltypes/arrays_test.go25 // ── Happy path ───────────────────────────────────────────────────────────COMMENT
MEDIUMgo/common/sqltypes/arrays_test.go96 // ── Backslash escaping outside of quotes ─────────────────────────────────COMMENT
MEDIUMgo/common/sqltypes/arrays_test.go118 // ── NULL handling ─────────────────────────────────────────────────────────COMMENT
MEDIUMgo/common/sqltypes/arrays_test.go138 // ── Unicode ───────────────────────────────────────────────────────────────COMMENT
MEDIUMgo/common/sqltypes/arrays_test.go146 // ── Structural errors ─────────────────────────────────────────────────────COMMENT
MEDIUMgo/common/sqltypes/sqltypes.go70// ─────────────────────────────────────────────────────────COMMENT
MEDIUM⚡go/services/multiorch/recovery/engine.go48// ┌──────────────────────────────────────────────────────────────────┐COMMENT
MEDIUM⚡go/services/multiorch/recovery/engine.go50// ├──────────────────────────────────────────────────────────────────┤COMMENT
MEDIUM⚡go/services/multiorch/recovery/engine.go52// │ ┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐ │COMMENT
MEDIUM⚡go/services/multiorch/recovery/engine.go55// │ └────────┬────────┘ └────────┬────────┘ └────────┬────────┘ │COMMENT
MEDIUM⚡go/services/multiorch/recovery/engine.go57// │ └────────────────────┼────────────────────┘ │COMMENT
MEDIUM⚡go/services/multiorch/recovery/engine.go60// └──────────────────────────────────────────────────────────────────┘COMMENT
MEDIUM⚡go/services/multiorch/recovery/engine.go86// ┌──────────────────────┐ ManagerHealthStream ┌──────────────────────┐COMMENT
MEDIUM⚡go/services/multiorch/recovery/engine.go87// │ Multipooler │ ──── snapshot ────────> │ HealthStream │COMMENT
MEDIUM⚡go/services/multiorch/recovery/engine.go89// │ 5s poll ticker) │ └──────────┬───────────┘COMMENT
MEDIUM⚡go/services/multiorch/recovery/engine.go90// └──────────────────────┘ │ applySnapshotCOMMENT
MEDIUM⚡go/services/multiorch/recovery/engine.go92// ┌──────────────────────┐COMMENT
MEDIUM⚡go/services/multiorch/recovery/engine.go94// └──────────────────────┘COMMENT
MEDIUM⚡go/services/multiorch/recovery/engine.go103// ┌──────────────────────┐COMMENT
MEDIUM⚡go/services/multiorch/recovery/engine.go104// │ Pooler Store │──────────┐COMMENT
MEDIUM⚡go/services/multiorch/recovery/engine.go106// └──────────────────────┘ │COMMENT
MEDIUM⚡go/services/multiorch/recovery/engine.go108// ┌──────────────────────┐COMMENT
MEDIUM⚡go/services/multiorch/recovery/engine.go111// └──────────┬───────────┘COMMENT
MEDIUM⚡go/services/multiorch/recovery/engine.go114// ┌──────────────────────┐COMMENT
MEDIUM⚡go/services/multiorch/recovery/engine.go117// └──────────┬───────────┘COMMENT
MEDIUM⚡go/services/multiorch/recovery/engine.go120// ┌──────────────────────┐COMMENT
MEDIUM⚡go/services/multiorch/recovery/engine.go123// └──────────┬───────────┘COMMENT
MEDIUM⚡go/services/multiorch/recovery/engine.go126// ┌──────────────────────┐COMMENT
MEDIUM⚡go/services/multiorch/recovery/engine.go129// └──────────┬───────────┘COMMENT
MEDIUM⚡go/services/multiorch/recovery/engine.go132// ┌──────────────────────┐COMMENT
MEDIUM⚡go/services/multiorch/recovery/engine.go135// └──────────────────────┘COMMENT
MEDIUM⚡…multipooler/internal/connpoolmanager/demand_tracker.go60// ┌─────────────────────────────────────────────────────────────┐COMMENT
MEDIUM⚡…multipooler/internal/connpoolmanager/demand_tracker.go62// ├───────────────────┬───────────────────┬─────────────────────┤COMMENT
MEDIUM⚡…multipooler/internal/connpoolmanager/demand_tracker.go66// └───────────────────┴───────────────────┴─────────────────────┘COMMENT
AI Slop Vocabulary16 hits · 52 pts
SeverityFileLineSnippetContext
MEDIUMcodecov.yml19 # PostgreSQL regression / isolation harness lives behind opt-in envCOMMENT
MEDIUM⚡codecov.yml37 # Shared harness helpers (patch verify/generate, corpus discovery, theCOMMENT
MEDIUM⚡codecov.yml44 # Row-path micro-benchmarks and the pgbench / large-result benchmark harnessCOMMENT
MEDIUM⚡codecov.yml46 # not the coverage-collecting CI, so their non-test lines (harness helpers)COMMENT
MEDIUMtools/safe_download.sh16# safe_download - A robust wrapper around curl for downloading filesCOMMENT
MEDIUMtools/setup_build_tools.sh573 # Install sqllogictest-rs CLI (used by the differential SLT harness).COMMENT
MEDIUMtools/setup_build_tools.sh576 # Build pgproto from source (used by the wire-protocol conformance harness).COMMENT
MEDIUMgo/tools/telemetry/sampler.go204 // to make matching more robust and explicit. For example:COMMENT
MEDIUMgo/test/endtoend/metrics/metrics_test.go336 // but captured as deltas so the test is robust to any residue).COMMENT
MEDIUMgo/test/endtoend/pgregresstest/extensions.go103 {"pg_jsonschema", KindExternal, StatusCovered, "Rust/pgrx JSON Schema validator; ships no SQL suite (upstream tests areCODE
MEDIUM…st/endtoend/subscriptionwire/subscription_wire_test.go101 // poll to be robust against any lag, then read its recorded state.COMMENT
MEDIUMgo/common/servenv/servenv_unix.go258 // #nosec G703 -- testDataDir comes from MULTIGRES_TESTDATA_DIR (test harness env), not external input.COMMENT
MEDIUMgo/common/pgprotocol/server/conn.go151 // keeps the check robust if c.conn is ever wrapped in instrumentation.COMMENT
MEDIUMgo/common/parser/plpgsql/read_construct.go43// token's start .. terminator's start), which is robust to how the lexer groupsCOMMENT
MEDIUMgo/services/multipooler/internal/executor/executor.go869// this is robust against pg_try_advisory_lock calls that failed, keys lockedCOMMENT
MEDIUMscripts/go_test_coverage.sh16# Development helper script for collecting comprehensive coverage data.COMMENT
Modern AI Meta-Vocabulary16 hits · 50 pts
SeverityFileLineSnippetContext
MEDIUM⚡codecov.yml38 # differential report core, schema-reset and run-loop scaffolding). TheCOMMENT
MEDIUMdemo/observability/sampling-config.yaml12 # Operations: orchestration, failover, replication managementCOMMENT
MEDIUMdemo/observability/sampling-config.yaml37 # MultipoolerManager: orchestration and replication managementCOMMENT
MEDIUM…rvices/multigateway/engine/apply_session_state_test.go1015// TestPinnedRouteTracksLiteralWhenNotReported pins the two guardrails on theCOMMENT
MEDIUMgo/services/multipooler/internal/manager/rpc_manager.go81 // Check REPLICA guardrails (recovery mode)COMMENT
MEDIUMgo/services/multipooler/internal/manager/rpc_manager.go238 // Check REPLICA guardrails (recovery mode)COMMENT
MEDIUMgo/services/multipooler/internal/manager/rpc_manager.go268 // Check REPLICA guardrails (recovery mode)COMMENT
MEDIUMgo/services/multipooler/internal/manager/rpc_manager.go301 // Check REPLICA guardrails (recovery mode)COMMENT
MEDIUMgo/services/multipooler/internal/manager/rpc_manager.go376 // Acting as primary - get primary status (skip guardrails since we already checked recovery mode)COMMENT
MEDIUMgo/services/multipooler/internal/manager/rpc_manager.go386 // Acting as standby - get replication status (skip guardrails since we already checked recovery mode)COMMENT
MEDIUMgo/services/multipooler/internal/manager/rpc_manager.go442 // Check PRIMARY guardrails (non-recovery mode)COMMENT
MEDIUMgo/services/multipooler/internal/manager/rpc_manager.go676 // Check PRIMARY guardrails (non-recovery mode)COMMENT
MEDIUMgo/services/multipooler/internal/manager/rpc_manager.go695 // Check PRIMARY guardrails (non-recovery mode)COMMENT
MEDIUMgo/services/multipooler/internal/manager/rpc_manager.go717 // Check REPLICA guardrails (recovery mode)COMMENT
MEDIUMconfig/multiorch.yaml2# Cluster orchestration service configurationCOMMENT
MEDIUMdocs/query_serving/testing_strategy.md318### `multigres.unsafe_connection` for a handful of scaffolding filesCOMMENT
Redundant / Tautological Comments19 hits · 28 pts
SeverityFileLineSnippetContext
LOWdemo/local/run-with-otel.sh9# Check if observability stack is runningCOMMENT
LOWdemo/local/run-observability.sh13# Check if docker is runningCOMMENT
LOWdemo/local/run-observability.sh19# Check if container is already runningCOMMENT
LOWtools/setup_s3_cluster.sh131# Check if cluster already existsCOMMENT
LOWtools/setup_build_tools.sh77 # Check if already installed with correct versionCOMMENT
LOWtools/setup_build_tools.sh305 # Check if PostgreSQL repo is already configuredCOMMENT
LOWgo/test/endtoend/run_in_test.sh78 # Check if testdata directory was deletedCOMMENT
LOWgo/test/endtoend/run_in_test.sh85 # Check if monitored process diedCOMMENT
LOWgo/test/endtoend/run_command_if_parent_dies.sh43 # Check if testdata directory was deletedCOMMENT
LOW…mon/parser/testdata/postgres/convert_postgres_tests.py80 # Check if we're starting a function body or DO blockCOMMENT
LOW…mon/parser/testdata/postgres/convert_postgres_tests.py127 # Check if we're ending a function body or DO blockCOMMENT
LOW…mon/parser/testdata/postgres/convert_postgres_tests.py154 # Check if statement ends after the definitionCOMMENT
LOW…mon/parser/testdata/postgres/convert_postgres_tests.py188 # Check if statement ends after the definitionCOMMENT
LOW…mon/parser/testdata/postgres/convert_postgres_tests.py200 # Check if statement ends with semicolon (but ONLY when not inside function body)COMMENT
LOW…mon/parser/testdata/postgres/convert_postgres_tests.py341 # Check if the statement contains psql variables (colon syntax)COMMENT
LOW…mon/parser/testdata/postgres/convert_postgres_tests.py407 # Check if this looks like a time patternCOMMENT
LOWscripts/go_test_coverage.sh54# Check if coverage binaries existCOMMENT
LOWscripts/go_test_coverage.sh130# Check if we have coverage data to mergeCOMMENT
LOWscripts/portpool.sh21# scripts/portpool.sh status # Check if the server is runningCOMMENT
Example Usage Blocks11 hits · 16 pts
SeverityFileLineSnippetContext
LOWdemo/k8s/backup-restore.sh27# Usage:COMMENT
LOWdocker/pgregress-generate.sh22# Usage:COMMENT
LOWgo/tools/retry/retry.go25// Example usage:COMMENT
LOWgo/tools/retry/retry.go193// Example usage:COMMENT
LOWgo/tools/timer/periodic_runner.go46// Example usage:COMMENT
LOWgo/tools/viperutil/registry.go48// Example usage:COMMENT
LOWgo/tools/viperutil/viper.go142// Example usage:COMMENT
LOWgo/provisioner/provisioner.go26// Example usage:COMMENT
LOWgo/common/parser/ast/rewriter_api.go33// Example usage:COMMENT
LOWgo/common/parser/ast/plpgsqlast/rewriter_api.go37// Example usage:COMMENT
LOWscripts/portpool.sh18# Usage:COMMENT
Fake / Example Data11 hits · 14 pts
SeverityFileLineSnippetContext
LOWgo/common/pgprotocol/server/query_test.go269 []byte("John Doe"),CODE
LOWgo/common/pgprotocol/client/query.go69 // - SELECT * FROM users WHERE email = 'user@example.com'COMMENT
LOWgo/common/parser/testdata/misc_cases.json664 "query": "CALL update_user(123, 'John Doe')"CODE
LOWgo/common/parser/testdata/misc_cases.json729 "query": "EXECUTE multi_param_plan (123, 'John Doe', TRUE)",CODE
LOWgo/common/parser/testdata/misc_cases.json730 "expected": "EXECUTE multi_param_plan ( 123, 'John Doe', TRUE )"CODE
LOW⚡go/common/parser/testdata/postgres/tsearch.json560 "query": "SELECT ts_headline('english', 'Lorem ipsum urna. Nullam nullam ullamcorper urna.', to_tsquery('english','CODE
LOW⚡go/common/parser/testdata/postgres/tsearch.json561 "expected": "SELECT ts_headline('english', 'Lorem ipsum urna. Nullam nullam ullamcorper urna.', to_tsquery('englishCODE
LOW⚡go/common/parser/testdata/postgres/tsearch.json565 "query": "SELECT ts_headline('english', 'Lorem ipsum urna. Nullam nullam ullamcorper urna.', phraseto_tsquery('englCODE
LOW⚡go/common/parser/testdata/postgres/tsearch.json566 "expected": "SELECT ts_headline('english', 'Lorem ipsum urna. Nullam nullam ullamcorper urna.', phraseto_tsquery('eCODE
LOWgo/common/parser/testdata/postgres/tsearch.json589 "query": "SELECT ts_headline('english', 'Lorem ipsum urna. Nullam nullam ullamcorper urna.', to_tsquery('english','CODE
LOWgo/common/parser/testdata/postgres/tsearch.json590 "expected": "SELECT ts_headline('english', 'Lorem ipsum urna. Nullam nullam ullamcorper urna.', to_tsquery('englishCODE
Self-Referential Comments3 hits · 8 pts
SeverityFileLineSnippetContext
MEDIUMdemo/local/run-observability.sh53# Create a temporary directory for dashboard provisioning configCOMMENT
MEDIUMtools/tool_checksums.sh17# This file contains verified checksums for binary downloads used in the project.COMMENT
MEDIUMgo/cmd/multigres/command/root.go60 multigres cluster init # Create a local cluster configurationCODE
Deep Nesting5 hits · 5 pts
SeverityFileLineSnippetContext
LOW…mon/parser/testdata/postgres/convert_postgres_tests.py44CODE
LOW…mon/parser/testdata/postgres/convert_postgres_tests.py244CODE
LOW…mon/parser/testdata/postgres/convert_postgres_tests.py292CODE
LOW…mon/parser/testdata/postgres/convert_postgres_tests.py328CODE
LOW…mon/parser/testdata/postgres/convert_postgres_tests.py361CODE
Hyper-Verbose Identifiers4 hits · 4 pts
SeverityFileLineSnippetContext
LOW…mon/parser/testdata/postgres/convert_postgres_tests.py292def extract_content_after_metacommand(line: str) -> str:CODE
LOW…mon/parser/testdata/postgres/convert_postgres_tests.py328def handle_parameterized_queries(stmt: str) -> Optional[str]:CODE
LOWweb/multiadmin/components/topology-graph.tsx95function calculateLagFromTimestamp(timestamp: string): string {CODE
LOWweb/multiadmin/components/ui/chart.tsx308function getPayloadConfigFromPayload(CODE
Excessive Try-Catch Wrapping1 hit · 1 pts
SeverityFileLineSnippetContext
LOW…mon/parser/testdata/postgres/convert_postgres_tests.py618 except Exception as e: # pylint: disable=broad-exception-caughtCODE