Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

psql terminal fails to launch

Abierto
  • ¿Algo no está bien?
#310 4 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
postgresql
Área
databases, devtools

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
Sin datos de lenguaje
Estrellas
399
Forks
33
Merge medio
1 d 9 h
PR fusionados (30 d)
2

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de microsoft/vscode-pgsql

Todos los issues de microsoft/vscode-pgsql

Issues similares

Más issues de Databases

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.