Cannot view database schema

[dongreensmith]

Describe issue:
When i try to expand schemas i receive the message "Error loading; refresh to try again"

Steps to Reproduce:
1.
2.
3.

Expected Behavior:

Actual Behavior:

---

Software	Version
PGSQL Extension	1.22.1
VS Code	1.121.0
OS	Darwin 25.5.0

[mmcfarland]

Hi @dongreensmith -- thanks for the report. Do you have any additional information you could share about reproducing this? Does it only happen on a single server/db/schema, or is it a problem with all of your connections? What version of PG is the server?

Also, is there anything about the error in the logs from the commannd "PGSQL: Show PostgreSQL Tools Service Logs"?

[dongreensmith]

Hi Matt, Thanks for this response. The error message I receive is pgsql: Failed to deep refresh: syntax error at or near "information_schema" LINE 8: OR nsp.nspname = 'information_schema' ^ When I retrieve the error from my postgres error log, I get [42601] syntax error at or near information_schema Severity: ERROR Command: idle User: don Database: transport Connection: 172.17.14.103:57260 rogue.mel.transport SELECT nsp.oid, nsp.nspname as name, has_schema_privilege(nsp.oid, 'CREATE') as can_create, has_schema_privilege(nsp.oid, 'USAGE') as has_usage, CASE WHEN nsp.nspname LIKE 'pg_%' ESCAPE '' OR nsp.nspname = 'information_schema' THEN true ELSE false END as is_system FROM pg_namespace nsp ORDER BY nspname; This same error occurs on all of my servers (I tried it on 13 servers). They are running PostgreSQL 16. Strangely when I copy the query from the error message and run it it returns a correct result. If I select the Dashboard for a server and then select visualize schema it runs correctly. I hope this clarifies matters for you. Regards Don

…

On Tue, 26 May 2026 at 23:01, Matt McFarland ***@***.***> wrote: *mmcfarland* left a comment (microsoft/vscode-pgsql#267) <#267 (comment)> Hi @dongreensmith <https://github.com/dongreensmith> -- thanks for the report. Do you have any additional information you could share about reproducing this? Does it only happen on a single server/db/schema, or is it a problem with all of your connections? What version of PG is the server? Also, is there anything about the error in the logs from the commannd "PGSQL: Show PostgreSQL Tools Service Logs"? — Reply to this email directly, view it on GitHub <#267?email_source=notifications&email_token=AA6YRV55N7SYLC7T3TQR6KL44WIRDA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINJUGQZDCNJYGI42M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4544215829>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA6YRV6X37GP64Q2SRNGNT344WIRDAVCNFSM6AAAAACZM6O7Z6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DKNBUGIYTKOBSHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[mmcfarland]

That's really helpful, thanks for all that detail. I'll look into this and follow up here.

[mmcfarland]

Hi @dongreensmith -- I've got a root cause suspected, and we could confirm it with a one-line query.

 SHOW standard_conforming_strings;

• Returns off → confirms the trigger for this bug.
• Returns on → not this issue.

A couple of useful variations:

 -- See where the setting comes from (config file, per-database, per-role, session, etc.)
 SELECT setting, source FROM pg_settings WHERE name = 'standard_conforming_strings';

 -- Reproduce the exact parse failure directly, no Object Explorer needed:
SET standard_conforming_strings = off;
SELECT 1 WHERE current_schema() LIKE 'pg\_%' ESCAPE '\'
            OR current_schema() = 'information_schema';
 -- ERROR: 42601 syntax error at or near "information_schema"

The fix would be on our side to generate a portable query that works with both on/off values of conforming_strings.

[dongreensmith]

Hi Matt, I executed these commands and it showed standard_conforming_strings off. Your test command failed as you expected. When I set standard_conforming_strings on your test command succeeded. regards Don

…

On Sat, 30 May 2026 at 03:56, Matt McFarland ***@***.***> wrote: *mmcfarland* left a comment (microsoft/vscode-pgsql#267) <#267 (comment)> Hi @dongreensmith <https://github.com/dongreensmith> -- I've got a root cause suspected, and we could confirm it with a one-line query. SHOW standard_conforming_strings; - Returns off → confirms the trigger for this bug. - Returns on → not this issue. A couple of useful variations: -- See where the setting comes from (config file, per-database, per-role, session, etc.) SELECT setting, source FROM pg_settings WHERE name = 'standard_conforming_strings'; -- Reproduce the exact parse failure directly, no Object Explorer needed: SET standard_conforming_strings = off; SELECT 1 WHERE 'x' LIKE 'pg\_%' ESCAPE '\' OR 'x' = 'information_schema'; --> ERROR: 42601 syntax error at or near "information_schema" The fix would be on our side to generate a portable query that works with both on/off values of conforming_strings. — Reply to this email directly, view it on GitHub <#267?email_source=notifications&email_token=AA6YRV3KOYU2HEWIHIW52VL45HFMZA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINJXHAZDANBWGMZ2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4578204633>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA6YRV43G6XTEMOS7LHFTUL45HFMZAVCNFSM6AAAAACZM6O7Z6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DKNZYGIYDINRTGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[mmcfarland]

Thanks for the help confirming, @dongreensmith. We've rolled out a fix for this in v1.25.0 (a pre-release). Could you install that version and let us know if you can expand cleanly now?

[dongreensmith]

Yes, it works! Thank you Regards Don

…

On Sun, 28 Jun 2026 at 04:16, Matt McFarland ***@***.***> wrote: *mmcfarland* left a comment (microsoft/vscode-pgsql#267) <#267 (comment)> Thanks for the help confirming, @dongreensmith <https://github.com/dongreensmith>. We've rolled out a fix for this in v1.25.0 (a pre-release). Could you install that version and let us know if you can expand cleanly now? — Reply to this email directly, view it on GitHub <#267?email_source=notifications&email_token=AA6YRVYF2FMLPBYFDFBRWU35CAFRXA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBRHE4TSNZWGAZKM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4819997602>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA6YRV7DKCBIVT2FTLGCP2T5CAFRXAVCNFSNUABFKJSXA33TNF2G64TZHM4TMOBYGE2TGMBZHNEXG43VMU5TINJSGA4TANZVG442C5QC> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[mmcfarland]

Great, thanks again for the report!