exception: access violation writing 0x0000000000000000

[Bilge]

Describe the bug

Connecting to any local server now gives: exception: access violation writing 0x0000000000000000. Really nice update guys.

To Reproduce

Steps to reproduce the behavior:

1. Connect to (previously defined) local server.

Expected behavior

Connects.

Error message

exception: access violation writing 0x0000000000000000

Screenshots

Desktop (please complete the following information):

• OS: Windows
• pgAdmin version: 9.18
• Mode: Desktop
• Browser (if running in server mode): n/a
• Package type: Windows installer

Additional context

Previous version worked without issue.

[dev-hari-prasad]

Duplicate of #10428

Please check #10428 for solution and consider closing this issue.

Thanks

[Bilge]

Nah, I'm keeping it open because this is such a monumental fuckup with no actual solution yet. I had to uninstall 9.18 to reinstall 9.17; couldn't even install over the top, because the obnoxious installer refuses to proceed if it detects a newer version installed.

[dev-hari-prasad]

There is a temporary workaround for this:

1. In the Object Explorer, right-click your server and select Properties (or configure it when registering a new server).
2. Go to the Parameters tab.
3. Click the + button to add a new parameter:
4. Name: GSS encmode (or gssencmode)
5. Value: disable
6. Click Save and reconnect.

Or by downgrading to 9.17.

[crimsonking98]

GSS encmode worked for me as well, thanks buddy

[Bilge]

Get AI to write you some regression tests because it's absurd that you can ship a version, that will remain current for another month, that cannot even connect to any database.

[ERPZI]

9.17 introduced an issue failing to remember your last-visited directory. And now this.
The temporary workaround works though. Thanks for that.

[dpage]

Duplicate of #10428, where I have posted the root cause and the workaround; please follow along there. In short, the PostgreSQL 18 libpq we ship with 9.18 is built with GSSAPI support and 9.17 was not, so any server that accepts GSS encryption now takes libpq into the Kerberos DLLs and it crashes. Setting GSS encmode to disable on the server avoids it in the meantime.