Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

psql terminal fails to launch

Aberta
  • Algo errado?
#310 4 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
35/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
postgresql
Domínio
databases, devtools

Direção de pesquisa

Start by reproducing on Windows with psql on PATH: run the context-menu action "pgsql.psqlTerminalDatabase" and the command "PGSQL: Connect with PSQL" with a connection open, and compare the two errors ("reading '1'" and "reading 'connectionInfo'"). The payload names no source files, so locate the psql terminal command in the extension and find where it reads the connection and the active database. Read the four existing comments for any diagnosis first. Done means the terminal opens connected to the selected database on Windows, with the reproduction steps confirmed.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

bug

Describe the bug

When launching a psql terminal from the context menu in the Postgresql database explorer panel, the terminal fails to launch with the following error message.

Error running command pgsql.psqlTerminalDatabase: Cannot read properties of null (reading '1'). This is likely caused by the extension that contributes pgsql.psqlTerminalDatabase.

When launching the terminal from the command pallette "PGSQL: Connect with PSQL" with an open database active the error message is slightly different:

Command 'PGSQL: Connect with PSQL' resulted in an error: Cannot read properties of undefined (reading 'connectionInfo')

psql exetubale is included in my windows path and is found with where psql.

$ where psql
C:\Users\<user>\AppData\Local\Programs\pgAdmin 4\runtime\psql.exe
C:\Program Files\QGIS 3.40.14\bin\psql.exe

It happens on all my postgresql connections, so also on for example:

       {
            "id": "6C6AC2B3-AA2E-4EE3-9E34-AA44EB883807",
            "groupId": "E9E9C702-BC45-4E78-A04C-9CF782103D09",
            "authenticationType": "SqlLogin",
            "connectTimeout": 15,
            "applicationName": "vscode-pgsql",
            "clientEncoding": "utf8",
            "sslmode": "prefer",
            "sshSavePassword": true,
            "savePassword": true,
            "sslRootCertMode": "none",
            "server": "localhost",
            "user": "postgres",
            "password": "",
            "database": "bce_models",
            "profileName": "bce-postgres-local",
            "expiresOn": 0,
            "sshPassword": "",
            "profileSource": 0,
            "displayName": "bce-postgres-local"
        }

To Reproduce

See the description of the bug.

Expected behavior

psql terminal is launched connected to the selected Postgresql database.

VS Code version

Version: 1.141.0 (user setup)
Commit: 2a59476c9bfcb90b3ddc372c36762471b7dfad1c
Date: 2026-10-06T10:15:52+02:00
Electron: 43.7.7
ElectronBuildId: 15553055
Chromium: 150.0.7871.250
Node.js: 24.21.0
V8: 15.0.245.31-electron.0
@github/copilot: 1.0.92-4.unstable.r37397886721.gad270aa
@github/copilot-sdk: 1.0.17.37397886721.gad270aa
OS: Windows_NT x64 10.0.26200

Extension Version and Logs

Extension version ms-ossdata.vscode-pgsql 1.32.0

Relevant Extension output

...

<img width="411" height="175" alt="Image" src="https://github.com/user-attachments/assets/8d44219f-49b0-44f7-a891-a51b818558f6" />

[11:58:01 AM] Connected to server "localhost" on document "6C6AC2B3-AA2E-4EE3-9E34-AA44EB883807". Server information: {"isCloud":false,"server":"PostgreSQL","serverVersion":"15.13"}
[11:59:05 AM] [PgToolsService Initialization] [Information]: Target is pg version 15.13

Add any other context about the problem here.

Windows 11 platform

Linguagem predominante
Sem dados de linguagem
Estrelas
399
Forks
33
Merge médio
1d 9h
PRs com merge (30d)
2

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de microsoft/vscode-pgsql

Todas as issues de microsoft/vscode-pgsql

Issues semelhantes

Mais issues de Databases

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.