Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

`graphql.resolve` crashes backend process on invalid `BigInt` filter value (`signal 6`, Postgres enters recovery)

Aperta
  • Qualcosa non va?
#641 1 commento 0 reazioni 1 assegnatario Vedi su GitHub

@olirice ci sta già lavorando.

Dal 14/5/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

triage-required

Describe the bug
pg_graphql crashes a PostgreSQL backend process (SIGABRT / signal 6) when a GraphQL filter passes a non-numeric string to a BigInt field.

Instead of returning a GraphQL validation/coercion error, the backend process is terminated while running:

SELECT graphql.resolve($1, $2, $3)
After that, Postgres restarts and clients see recovery/pool errors

To Reproduce

  1. Ensure a GraphQL-exposed type has a BIGINT column (in our case this is version).
  2. Run this GraphQL operation through graphql.resolve:
query GetJobDetails($definitionFilter: jobDefinitionViewFilter, $runtimeFilter: jobsViewFilter) {
  jobDefinitionViewCollection(filter: $definitionFilter) {
    edges {
      node {
        id
        version
        displayName
      }
    }
  }
  jobsViewCollection(filter: $runtimeFilter, first: 1) {
    edges {
      node {
        state
      }
    }
  }
}
  1. Use variables where the BigInt-typed filter value is not numeric:
{
  "definitionFilter": {
    "environment": { "eq": "dev" },
    "name": { "eq": "job-name" },
    "version": { "eq": "not-an-int" }
  },
  "runtimeFilter": {
    "environment": { "eq": "dev" },
    "name": { "eq": "job-name" }
  }
}
  1. Observe PostgreSQL logs:
    • client backend ... was terminated by signal 6: Aborted
    • Failed process was running: SELECT graphql.resolve($1, $2, $3)
    • followed by recovery mode and pooler login failures.

Expected behavior
A clear and concise description of what you expected to happen.

The invalid BigInt input should return a normal GraphQL/SQL error (similar to invalid input syntax for type bigint) and should not crash the backend process.

Screenshots
If applicable, add screenshots to help explain your problem.

Versions:

  • PostgreSQL: PostgreSQL 18.1 on aarch64-unknown-linux-musl, compiled by gcc (Alpine 15.2.0) 15.2.0, 64-bit
  • pg_graphql commit ref: unknown in packaged build (extension version is 1.5.12)

Additional context

  • Plain Postgres cast handles this correctly without crashing:
    • SELECT 'not-an-int'::bigint; -> ERROR: invalid input syntax for type bigint: "not-an-int"
  • The crash appears specific to the graphql.resolve path.
  • Observed app-side error after crash:
    • Lost connection to the database server.

Security
If you beleive you have identified a security vulnerability in pg_graphql, please follow the instructions at security.txt and wait for a response before opening a GitHub issue.

Lingua principale
Rust
Stelle
3.4k
Fork
143
Merge medio
4h 47m
PR unite (30g)
2

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di supabase/pg_graphql

Tutte le issue di supabase/pg_graphql

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.