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

Documentation lists Aggregate, but feature not released in pg_graphql

Aperta
#602 12 commenti 1 reazione 1 assegnatario Vedi su GitHub

@olirice ci sta già lavorando.

Dal 30/8/2025.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

question

Describe the bug The Supabase GraphQL documentation mentions the possibility to enable aggregate fields using table comments (see: https://supabase.com/docs/guides/graphql/configuration#aggregate). However, when attempting to enable it on a Supabase Cloud project, the feature does not appear in the schema. This looks like either:

  • the feature is not yet released despite being documented, or
  • there is a bug in the extension where the configuration is silently ignored.

To Reproduce Steps to reproduce the behavior:

  1. On Supabase Cloud, with pg_graphql v1.5.11 (Postgres 17.4.1.074), open the SQL Editor.
  2. Run:
    comment on table "TableName" is e'@graphql({"aggregate": {"enabled": true}})';
    
  3. Go to the GraphQL schema explorer in Supabase Studio or introspect the schema via GraphQL.
  4. Notice that the aggregate field is not exposed on the type.

Expected behavior The GraphQL schema should expose an aggregate field on the BlogPost type when aggregate.enabled = true, as described in the documentation.

Screenshots No SQL error is returned when applying the comment, but the field is missing from the schema. Example from the GraphQL Explorer:

# Expected to see something like:

aggregate {
  count
  ...
}

# But aggregate is not present.

Versions:

  • PostgreSQL: 17.4.1.074
  • pg_graphql: 1.5.11 (Supabase Cloud)

Additional context

  • The related PR implementing aggregate support is https://github.com/supabase/pg_graphql/pull/589 (merged May 2025).
  • The last pg_graphql release on GitHub is from February 2025, so it seems the feature has not been released yet.
  • However, the Supabase documentation already describes aggregate as available, which creates confusion.

Security This is not a security 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.