Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

psql terminal fails to launch

Ouverte
  • Quelque chose ne va pas ?
#310 4 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
35/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
postgresql
Domaine
databases, devtools

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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

Langage dominant
Aucune donnée de langage
Étoiles
399
Forks
33
Merge moyen
1 j 9 h
PR mergées (30 j)
2

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de microsoft/vscode-pgsql

Toutes les issues de microsoft/vscode-pgsql

Issues similaires

Plus d'issues Databases

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.