graphql-engine
graphql-engine copied to clipboard
Neon pulled connection string problem on watch mode
Component
CLI -> c/v3-cli Postgres (for issues that clearly relates to Postgres SQL execution) -> c/v3-ndc-postgres
What is the current behaviour?
- starting a new project
- adding
hasura3 metadata add-hub-connector pg_db --dir . --subgraph default --id hasura/postgres --url "postgresql://user:pwd@uri/hs?sslmode=require"
- connector added and schema file created
- running
hasura3 watch --dir.
- error:
9:00AM ERR unable to refresh data connector connector config for /Users/tadeumaia/code/personal/invictus/apps/hasura/subgraphs/default/dataconnectors/pg_db/pg_db.hml error="error fetching ndc schema: Post \"https://config-proxy.pro.hasura.io/connectors/postgres\": context canceled"
What is the expected behaviour?
- starting a new project
- adding
hasura3 metadata add-hub-connector pg_db --dir . --subgraph default --id hasura/postgres --url "postgresql://user:pwd@uri/hs?sslmode=require"
- connector added and schema file created
- running
hasura3 watch --dir.
- no error message on watch
How to reproduce the issue?
- Create a free neon postgress database
- Get a connection string for pooled connection
- Create a table
- add that db to a plain hasura project created from scratch
Please provide any traces or logs that could help here.
error="error fetching connector schema: status: 500, message: error returned from database: prepared statement "sqlx_s_1" already exists"
Any possible solutions/workarounds you're aware of?
The engine does work and the connection was made, build created, but it keeps failing on watch mode.
Keywords
neon, pg