microsoft / microsoft/vscode-pgsql
Messages are not handled correctly
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 395
- Forks
- 33
- Avg merge
- 1h 46m
- Merged PRs (30d)
- 3
Description
Describe the bug
When executing PL/pgSQL, log messages sent by the RAISE NOTICE command are not handled correctly in the POSTGRESQL QUERY RESULTS.
The message is being trimmed, and it appears only when the execution finishes.
To Reproduce
Steps to reproduce the behavior:
- Execute the following PL/pgSQL command:
DO $$ DECLARE i INT; BEGIN FOR i IN 1..10 LOOP RAISE NOTICE '%-%-%', REPEAT(' ', i), CONCAT('Message ', i), REPEAT(' ', i); PERFORM pg_sleep(1); END LOOP; END $$;
Expected behavior
The message is not trimmed, and it appears immediately after execution.
VS Code version
1.107.1
Extension Version
1.14.0
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the PL/pgSQL example and inspect how POSTGRESQL QUERY RESULTS handles RAISE NOTICE output during execution. No source file or test is named; done means preserving the message's whitespace and displaying each notice immediately rather than only after execution finishes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, vscode
- Domain
- database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100