Repository navigation
How to debug the LSP / VS Code extensions when no suggestions? #320
|
I am trying out the postgrestools VS Code extension but having issues getting it to suggest tables/columns from my database. My config looks like this: {
"$schema": "https://raw.githubusercontent.com/supabase-community/postgres-language-server/refs/heads/main/docs/schemas/latest/schema.json",
"vcs": {
"enabled": true,
"clientKind": "git",
"useIgnoreFile": true
},
"files": {
"ignore": []
},
"linter": {
"enabled": true,
"rules": {
"recommended": true
}
},
"db": {
"host": "127.0.0.1",
"port": 5432,
"username": "***",
"password": "***",
"database": "***",
"connTimeoutSecs": 10
}
}Not getting any suggestions from my database schema: Screen.Recording.2025-04-07.at.11.48.45.AM.movVS Code output logs postgrestools: postgrestools LSP: postgrestools LSP trace: nothing |
Replies: 2 comments 1 reply
|
Hey, thanks for reporting! We are writing a logfile - could you paste that here? That will help in debugging. Where to find the logs: https://pgtools.dev/#daemon-logs |
|
This was on 0.3.1 and a lot has changed since. Please update to the latest CLI and VS Code extension. If completions are still missing, check the daemon log in the |
This was on 0.3.1 and a lot has changed since. Please update to the latest CLI and VS Code extension. If completions are still missing, check the daemon log in the
pgls-logsfolder (location in https://pg-language-server.com/latest/guides/ide_setup/#daemon-logs, configurable withPGLS_LOG_PATH) for database connection errors.postgres-language-server check <file>also reports a diagnostic when the database can't be reached. Closing as stale; feel free to reopen with a fresh log.