GraphQL variables break ndc-postgres execution plan

[arjunyel]

Component

c/v3-ndc-postgres

What is the current behaviour?

Connector execution plan when there is GraphQL variables always looks something like this

Aggregate  (cost=0.02..0.03 rows=1 width=32)
  ->  Aggregate  (cost=0.00..0.01 rows=1 width=32)
        ->  Result  (cost=0.00..0.00 rows=0 width=158)
              One-Time Filter: false

What is the expected behaviour?

Aggregate  (cost=14967.53..14967.54 rows=1 width=32)
  ->  Aggregate  (cost=14967.51..14967.52 rows=1 width=32)
        ->  Nested Loop Left Join  (cost=14964.48..14967.50 rows=1 width=158)
              ->  Nested Loop Left Join  (cost=4.21..7.20 rows=1 width=126)
                    ->  Nested Loop Left Join  (cost=1.17..4.13 rows=1 width=94)

...etc

How to reproduce the issue?

1. Do a ndc-postgres query using Graphql variables and check connector execution plan such as

query getGroup($id: Text!) {
  groupById(id: $id) {
    id
  }
}

2. Do a query without variable such as

query getGroup {
  groupById(id: "test") {
    id
  }
}

Screenshots or Screencast

Please provide any traces or logs that could help here.

1da2a28302891f9e5aa3ed9314f9f82b

vs

91f1667942a862e139df6c5c4894426d

Any possible solutions/workarounds you're aware of?

Keywords

Traces postgres query execution plan analyze