Repository Analysis

multigres/multigres

Vitess for Postgres

4.5 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of multigres/multigres, a Go project with 2,455 GitHub stars. SynthScan v2.0 examined 650,918 lines of code across 1735 source files, recording 2557 pattern matches distributed across 13 syntactic categories. The overall adjusted score of 4.5 places this repository in the Likely human-written band.

The scanner applied 160+ deterministic lexical heuristics, multi-line block detectors, abstract syntax tree depth profilers, and a cross-file Jaccard similarity matrix to construct a statistically normalised synthetic code estimate. All matches are individually weighted by severity coefficient and contextual multiplier before summation, and the resulting headline score is temporally discounted to account for the repository's development history relative to the commercial emergence of large language model coding tooling (November 2022 onward).

4.5
Adjusted Score
4.5
Raw Score
100%
Time Factor
2026-07-14
Last Push
2.5K
Stars
Go
Language
650.9K
Lines of Code
1.7K
Files
2.6K
Pattern Hits
2026-07-14
Scan Date
0.00
HC Hit Rate

What These Metrics Mean

Adjusted Score
Primary synthetic code indicator. Raw score normalised per 1,000 lines of code and multiplied by the temporal discount factor. This is the definitive comparative metric — use it to rank repositories by AI authorship density.
Raw Score
The unmodified sum of all severity-weighted, context-multiplied pattern match scores before temporal discounting. Reflects the absolute signal strength independent of when the repository was last active.
Time Factor
The temporal discount multiplier (0–100%) applied to the raw score. Repositories last updated before ChatGPT's launch (Nov 2022) receive a 5% factor. Full signal is only assigned to repositories active in the post-adoption era (Jan 2024+).
Pattern Hits
Total count of individual pattern matches across all files and categories. A high hit count with a low score may indicate a very large codebase with isolated AI snippets; a low count with a high score indicates dense, concentrated AI signatures.
HC Hit Rate
High+Critical pattern hits per file, averaged across the repository. This orthogonal signal catches repositories where a few files are densely packed with high-severity AI tells — a strong indicator even when the normalised score appears moderate due to codebase size.
Lines of Code / Files
Total lines and files analysed. The scanner examines 94 file extensions. These denominators are used to normalise the score, enabling fair comparison between repositories of vastly different sizes.

Score History

This chart maps the temporal evolution of the adjusted synthetic code score across successive scan runs. An upward trajectory indicates ongoing incorporation of AI-generated code or expanding LLM-assisted scaffolding; a stable or declining trajectory may reflect active human refactoring, code removal, or the adoption of stricter authorship policies. The dashed secondary line (right axis) independently tracks total raw pattern hit count, which can diverge from the normalised score when codebase size changes significantly between scans.

Severity Breakdown

Classifies detected patterns by their diagnostic confidence and structural impact. CRITICAL patterns (coefficient 10) represent definitive synthetic signatures — hallucinated imports, explicit LLM attribution metadata — virtually never produced by human authors. HIGH (5) indicates strong structural tells such as cross-file repetition or cross-linguistic idioms. MEDIUM (2) covers recognisable conversational padding and AI-specific vocabulary. LOW (1) captures subtle indicators like tautological comments and generic boilerplate that require density to carry independent signal.

CRITICAL 0HIGH 0MEDIUM 66LOW 2491

Directory Score Breakdown

This horizontal bar chart decomposes the repository's raw synthetic code score by top-level directory, allowing you to pinpoint precisely which modules or components carry the highest AI authorship density. Directories with disproportionately high scores relative to their size warrant targeted manual review: concentrated AI signatures often trace back to mass-generated configuration layers, auto-ported test suites, LLM-scaffolded boilerplate classes, or entire subsystems authored under heavy copilot assistance. Use this view to prioritise your human code-review effort.

Pattern Findings

The scanner identified 2557 distinct pattern matches across 13 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a statistically significant AI authorship indicator. 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 diagnostic confidence level (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — comment-context matches receive a ×1.5 weight because LLMs systematically over-annotate. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier as dense clusters constitute far stronger evidence of synthetic authorship than isolated hits.

Over-Commented Block2221 hits · 2206 pts
SeverityFileLineSnippetContext
LOWcodecov.yml1ignore:COMMENT
LOWcodecov.yml21 # exercised by the dedicated extended-suite workflow.COMMENT
LOW.golangci.yml1# Copyright 2025 Supabase, Inc.COMMENT
LOW.golangci.yml201 - deepequalerrorsCOMMENT
LOW.golangci.yml221 - ifaceassertCOMMENT
LOWdocker-compose.yml1# All-in-one Multigres cluster for local development and CI compatibilityCOMMENT
LOWdocker-compose.yml21 # bundles the required extensions + pgBackRest and setCOMMENT
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
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/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/metrics.go1// Copyright 2026 Supabase, Inc.COMMENT
LOWgo/cmd/pgctld/command/pg_instance_test.go1// Copyright 2026 Supabase, Inc.COMMENT
LOWgo/cmd/pgctld/command/pgdata_permissions_test.go1// Copyright 2026 Supabase, Inc.COMMENT
LOWgo/cmd/pgctld/command/start.go1// Copyright 2025 Supabase, Inc.COMMENT
LOWgo/cmd/pgctld/command/metrics_test.go1// Copyright 2026 Supabase, Inc.COMMENT
LOWgo/cmd/pgctld/command/crash_recovery_test.go1// Copyright 2026 Supabase, Inc.COMMENT
LOWgo/cmd/pgctld/command/root_test.go1// Copyright 2026 Supabase, Inc.COMMENT
LOWgo/cmd/pgctld/command/status_test.go1// Copyright 2025 Supabase, Inc.COMMENT
LOWgo/cmd/pgctld/command/pg_instance.go1// Copyright 2026 Supabase, Inc.COMMENT
LOWgo/cmd/pgctld/command/pg_instance.go21 "os"COMMENT
LOWgo/cmd/pgctld/command/pg_instance.go41// PostgreSQL server will use. If we started the transient server on thatCOMMENT
LOWgo/cmd/pgctld/command/stop.go1// Copyright 2025 Supabase, Inc.COMMENT
2161 more matches not shown…
Structural Annotation Overuse116 hits · 209 pts
SeverityFileLineSnippetContext
LOWgo/cmd/pgctld/command/server_test.go681 // Step 1: Simulate a running postgres by installing a postmaster.pid thatCOMMENT
LOWgo/cmd/pgctld/command/server_test.go686 // Step 2: Stop postgres. This is the first part of the stop→rewind→start sequence.COMMENT
LOWgo/cmd/pgctld/command/server_test.go691 // Step 3: Run pg_rewind (dry-run). The service must accept this call after a stop;COMMENT
LOWgo/cmd/pgctld/command/server_test.go701 // 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
LOWgo/test/s3mock/test-pgbackrest.sh220# Step 6: Extract backup label from info outputCOMMENT
LOWgo/test/s3mock/test-pgbackrest.sh230# Step 7: Verify backup integrityCOMMENT
LOWgo/test/s3mock/test-pgbackrest.sh239# Step 8: Test restoreCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go70 // Step 1: Check initial statusCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go75 // Step 2: Initialize data directoryCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go79 // Step 3: Start PostgreSQLCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go84 // Step 4: Check status - should be runningCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go90 // Step 5: Get versionCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go95 // Step 6: Reload configCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go100 // Step 7: RestartCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go105 // Step 8: Check status againCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go110 // Step 9: Stop PostgreSQLCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go115 // Step 10: Final status checkCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go362 // Step 1: Check initial status - should be NOT_INITIALIZEDCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go368 // Step 2: Try to start without initialization - should fail with proper errorCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go374 // Step 3: Try to stop without initialization - should return appropriate messageCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go384 // Step 4: Try restart without initialization - should failCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go389 // Step 5: Try reload config without initialization - should failCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go394 // Step 6: Initialize should workCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go399 // Step 7: Status should now show STOPPEDCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_test.go106 // Step 2: Check status - should show stopped after initCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_test.go116 // Step 3: Test help commands workCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_test.go122 // Step 4: Test that real PostgreSQL binaries are detectedCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_test.go129 // Step 5: Test initialization works with real PostgreSQLCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_test.go972 // Step 1: Initialize the database firstCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_test.go981 // Step 2: Check status - should be stopped after initCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_test.go991 // Step 3: Start PostgreSQLCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_test.go997 // Step 4: Check status - should be runningCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_test.go1004 // Step 5: Reload configurationCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_test.go1010 // Step 6: Restart PostgreSQLCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_test.go1016 // Step 7: Check status again - should still be runningCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_test.go1023 // Step 8: Stop PostgreSQLCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_test.go1029 // 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
LOWgo/test/endtoend/multiorch/demote_stale_primary_test.go98 // Step 1: Kill postgres on primary to trigger failoverCOMMENT
LOWgo/test/endtoend/multiorch/demote_stale_primary_test.go102 // Step 2: Wait for new primary electionCOMMENT
LOWgo/test/endtoend/multiorch/demote_stale_primary_test.go108 // Step 3: Write data to new primary to ensure timeline has divergedCOMMENT
LOWgo/test/endtoend/multiorch/demote_stale_primary_test.go112 // Step 4: Re-enable postgres auto-restarts on the old primary. The newCOMMENT
LOWgo/test/endtoend/multiorch/demote_stale_primary_test.go120 // Step 5: Wait for multiorch to detect and repair divergence. Once postgresCOMMENT
LOWgo/test/endtoend/multiorch/demote_stale_primary_test.go127 // Step 6: Verify old primary is now replicating from new primaryCOMMENT
LOWgo/test/endtoend/multiorch/demote_stale_primary_test.go131 // Step 7: Verify replication is actually working by writing data and checking it replicatesCOMMENT
LOWgo/test/endtoend/multiorch/demote_stale_primary_test.go135 // Step 8: Verify the old primary was demoted via SetPrimary.COMMENT
LOWgo/test/endtoend/multiorch/demote_stale_primary_test.go140 // Step 9: Verify consensus.recruit event was emitted during failover.COMMENT
LOWgo/test/endtoend/multiorch/demote_stale_primary_test.go196 // Step 1: Gracefully shutdown postgres on primary to trigger failover.COMMENT
LOWgo/test/endtoend/multiorch/demote_stale_primary_test.go204 // Step 2: Wait for new primary electionCOMMENT
56 more matches not shown…
Verbosity Indicators104 hits · 193 pts
SeverityFileLineSnippetContext
LOWgo/cmd/pgctld/command/server_test.go681 // Step 1: Simulate a running postgres by installing a postmaster.pid thatCOMMENT
LOWgo/cmd/pgctld/command/server_test.go686 // Step 2: Stop postgres. This is the first part of the stop→rewind→start sequence.COMMENT
LOWgo/cmd/pgctld/command/server_test.go691 // Step 3: Run pg_rewind (dry-run). The service must accept this call after a stop;COMMENT
LOWgo/cmd/pgctld/command/server_test.go701 // 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
LOWgo/test/s3mock/test-pgbackrest.sh220# Step 6: Extract backup label from info outputCOMMENT
LOWgo/test/s3mock/test-pgbackrest.sh230# Step 7: Verify backup integrityCOMMENT
LOWgo/test/s3mock/test-pgbackrest.sh239# Step 8: Test restoreCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go70 // Step 1: Check initial statusCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go75 // Step 2: Initialize data directoryCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go79 // Step 3: Start PostgreSQLCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go84 // Step 4: Check status - should be runningCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go90 // Step 5: Get versionCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go95 // Step 6: Reload configCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go100 // Step 7: RestartCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go105 // Step 8: Check status againCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go110 // Step 9: Stop PostgreSQLCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go115 // Step 10: Final status checkCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go362 // Step 1: Check initial status - should be NOT_INITIALIZEDCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go368 // Step 2: Try to start without initialization - should fail with proper errorCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go374 // Step 3: Try to stop without initialization - should return appropriate messageCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go384 // Step 4: Try restart without initialization - should failCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go389 // Step 5: Try reload config without initialization - should failCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go394 // Step 6: Initialize should workCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_grpc_test.go399 // Step 7: Status should now show STOPPEDCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_test.go106 // Step 2: Check status - should show stopped after initCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_test.go116 // Step 3: Test help commands workCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_test.go122 // Step 4: Test that real PostgreSQL binaries are detectedCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_test.go129 // Step 5: Test initialization works with real PostgreSQLCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_test.go972 // Step 1: Initialize the database firstCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_test.go981 // Step 2: Check status - should be stopped after initCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_test.go991 // Step 3: Start PostgreSQLCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_test.go997 // Step 4: Check status - should be runningCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_test.go1004 // Step 5: Reload configurationCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_test.go1010 // Step 6: Restart PostgreSQLCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_test.go1016 // Step 7: Check status again - should still be runningCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_test.go1023 // Step 8: Stop PostgreSQLCOMMENT
LOWgo/test/endtoend/pgctld/pgctld_test.go1029 // 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
LOWgo/test/endtoend/multiorch/demote_stale_primary_test.go98 // Step 1: Kill postgres on primary to trigger failoverCOMMENT
LOWgo/test/endtoend/multiorch/demote_stale_primary_test.go102 // Step 2: Wait for new primary electionCOMMENT
LOWgo/test/endtoend/multiorch/demote_stale_primary_test.go108 // Step 3: Write data to new primary to ensure timeline has divergedCOMMENT
LOWgo/test/endtoend/multiorch/demote_stale_primary_test.go112 // Step 4: Re-enable postgres auto-restarts on the old primary. The newCOMMENT
LOWgo/test/endtoend/multiorch/demote_stale_primary_test.go120 // Step 5: Wait for multiorch to detect and repair divergence. Once postgresCOMMENT
LOWgo/test/endtoend/multiorch/demote_stale_primary_test.go127 // Step 6: Verify old primary is now replicating from new primaryCOMMENT
LOWgo/test/endtoend/multiorch/demote_stale_primary_test.go131 // Step 7: Verify replication is actually working by writing data and checking it replicatesCOMMENT
LOWgo/test/endtoend/multiorch/demote_stale_primary_test.go135 // Step 8: Verify the old primary was demoted via SetPrimary.COMMENT
LOWgo/test/endtoend/multiorch/demote_stale_primary_test.go140 // Step 9: Verify consensus.recruit event was emitted during failover.COMMENT
LOWgo/test/endtoend/multiorch/demote_stale_primary_test.go196 // Step 1: Gracefully shutdown postgres on primary to trigger failover.COMMENT
LOWgo/test/endtoend/multiorch/demote_stale_primary_test.go204 // Step 2: Wait for new primary electionCOMMENT
44 more matches not shown…
Decorative Section Separators37 hits · 142 pts
SeverityFileLineSnippetContext
MEDIUMdemo/k8s/k8s-multipooler-statefulset.yaml11 # ===================================================COMMENT
MEDIUMgo/common/consensus/proposals_test.go220 // ── outgoing cohort mode ──────────────────────────────────────────────────COMMENT
MEDIUMgo/common/consensus/proposals_test.go1019 // ── 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
MEDIUMgo/services/multiorch/recovery/engine.go47// ┌──────────────────────────────────────────────────────────────────┐COMMENT
MEDIUMgo/services/multiorch/recovery/engine.go49// ├──────────────────────────────────────────────────────────────────┤COMMENT
MEDIUMgo/services/multiorch/recovery/engine.go51// │ ┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐ │COMMENT
MEDIUMgo/services/multiorch/recovery/engine.go54// │ └────────┬────────┘ └────────┬────────┘ └────────┬────────┘ │COMMENT
MEDIUMgo/services/multiorch/recovery/engine.go56// │ └────────────────────┼────────────────────┘ │COMMENT
MEDIUMgo/services/multiorch/recovery/engine.go59// └──────────────────────────────────────────────────────────────────┘COMMENT
MEDIUMgo/services/multiorch/recovery/engine.go85// ┌──────────────────────┐ ManagerHealthStream ┌──────────────────────┐COMMENT
MEDIUMgo/services/multiorch/recovery/engine.go86// │ Multipooler │ ──── snapshot ────────> │ HealthStream │COMMENT
MEDIUMgo/services/multiorch/recovery/engine.go88// │ 5s poll ticker) │ └──────────┬───────────┘COMMENT
MEDIUMgo/services/multiorch/recovery/engine.go89// └──────────────────────┘ │ applySnapshotCOMMENT
MEDIUMgo/services/multiorch/recovery/engine.go91// ┌──────────────────────┐COMMENT
MEDIUMgo/services/multiorch/recovery/engine.go93// └──────────────────────┘COMMENT
MEDIUMgo/services/multiorch/recovery/engine.go102// ┌──────────────────────┐COMMENT
MEDIUMgo/services/multiorch/recovery/engine.go103// │ Pooler Store │──────────┐COMMENT
MEDIUMgo/services/multiorch/recovery/engine.go105// └──────────────────────┘ │COMMENT
MEDIUMgo/services/multiorch/recovery/engine.go107// ┌──────────────────────┐COMMENT
MEDIUMgo/services/multiorch/recovery/engine.go110// └──────────┬───────────┘COMMENT
MEDIUMgo/services/multiorch/recovery/engine.go113// ┌──────────────────────┐COMMENT
MEDIUMgo/services/multiorch/recovery/engine.go116// └──────────┬───────────┘COMMENT
MEDIUMgo/services/multiorch/recovery/engine.go119// ┌──────────────────────┐COMMENT
MEDIUMgo/services/multiorch/recovery/engine.go122// └──────────┬───────────┘COMMENT
MEDIUMgo/services/multiorch/recovery/engine.go125// ┌──────────────────────┐COMMENT
MEDIUMgo/services/multiorch/recovery/engine.go128// └──────────┬───────────┘COMMENT
MEDIUMgo/services/multiorch/recovery/engine.go131// ┌──────────────────────┐COMMENT
MEDIUMgo/services/multiorch/recovery/engine.go134// └──────────────────────┘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
Modern AI Meta-Vocabulary15 hits · 45 pts
SeverityFileLineSnippetContext
MEDIUMcodecov.yml32 # 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
MEDIUMgo/services/multipooler/internal/manager/rpc_manager.go59 // Check REPLICA guardrails (pooler type and recovery mode)COMMENT
MEDIUMgo/services/multipooler/internal/manager/rpc_manager.go217 // Check REPLICA guardrails (pooler type and recovery mode)COMMENT
MEDIUMgo/services/multipooler/internal/manager/rpc_manager.go247 // Check REPLICA guardrails (pooler type and recovery mode)COMMENT
MEDIUMgo/services/multipooler/internal/manager/rpc_manager.go280 // Check REPLICA guardrails (pooler type and recovery mode)COMMENT
MEDIUMgo/services/multipooler/internal/manager/rpc_manager.go342 // Acting as primary - get primary status (skip guardrails since we already checked recovery mode)COMMENT
MEDIUMgo/services/multipooler/internal/manager/rpc_manager.go352 // Acting as standby - get replication status (skip guardrails since we already checked recovery mode)COMMENT
MEDIUMgo/services/multipooler/internal/manager/rpc_manager.go379 // Check REPLICA guardrails (pooler type and recovery mode)COMMENT
MEDIUMgo/services/multipooler/internal/manager/rpc_manager.go431 // Check PRIMARY guardrails (pooler type and non-recovery mode)COMMENT
MEDIUMgo/services/multipooler/internal/manager/rpc_manager.go612 // Check PRIMARY guardrails (pooler type and non-recovery mode)COMMENT
MEDIUMgo/services/multipooler/internal/manager/rpc_manager.go631 // Check PRIMARY guardrails (pooler type and non-recovery mode)COMMENT
MEDIUMgo/services/multipooler/internal/manager/rpc_manager.go653 // Check REPLICA guardrails (pooler type and recovery mode)COMMENT
MEDIUMconfig/multiorch.yaml2# Cluster orchestration service configurationCOMMENT
AI Slop Vocabulary11 hits · 32 pts
SeverityFileLineSnippetContext
MEDIUMcodecov.yml17 # PostgreSQL regression / isolation harness lives behind opt-in envCOMMENT
MEDIUMcodecov.yml31 # Shared harness helpers (patch verify/generate, corpus discovery, theCOMMENT
MEDIUMtools/safe_download.sh16# safe_download - A robust wrapper around curl for downloading filesCOMMENT
MEDIUMtools/setup_build_tools.sh571 # Install sqllogictest-rs CLI (used by the differential SLT harness).COMMENT
MEDIUMtools/setup_build_tools.sh574 # 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/pgregresstest/extensions.go103 {"pg_jsonschema", KindExternal, StatusCovered, "Rust/pgrx JSON Schema validator; ships no SQL suite (upstream tests areCODE
MEDIUMgo/common/servenv/servenv_unix.go233 // #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/services/multipooler/internal/executor/executor.go738// 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
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 Blocks10 hits · 15 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.go46// 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
LOWscripts/portpool.sh18# Usage:COMMENT
Fake / Example Data11 hits · 14 pts
SeverityFileLineSnippetContext
LOWgo/common/pgprotocol/server/query_test.go268 []byte("John Doe"),CODE
LOWgo/common/pgprotocol/client/query.go65 // - 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
LOWgo/common/parser/testdata/postgres/tsearch.json560 "query": "SELECT ts_headline('english', 'Lorem ipsum urna. Nullam nullam ullamcorper urna.', to_tsquery('english','CODE
LOWgo/common/parser/testdata/postgres/tsearch.json561 "expected": "SELECT ts_headline('english', 'Lorem ipsum urna. Nullam nullam ullamcorper urna.', to_tsquery('englishCODE
LOWgo/common/parser/testdata/postgres/tsearch.json565 "query": "SELECT ts_headline('english', 'Lorem ipsum urna. Nullam nullam ullamcorper urna.', phraseto_tsquery('englCODE
LOWgo/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