View Issue Details

IDProjectCategoryView StatusLast Update
0006763Kali LinuxTool Upgrade Requestpublic2022-03-28 09:15
Reporterklbt001 Assigned Todaniruiz  
Status closedResolutionno change required 
Product Version2020.3 
Summary0006763: Current gvm 11 is very slow with PostgreSQL 12

Current gvm 11.0.5 is very slow with PostgreSQL 12.4.

This is because gvm 11 is optimized for PostgreSQL 9.6, but Kali ships 12.4.

See this forum message from Björn Ricks, the GVM development team lead:

If PostgreSQL 12 will receive fixes in gvm 20 and gvm 21 isn't promised.
Please see this forum message of Björn Ricks:

Steps To Reproduce

Create and execute a vulnerability scan that produces about 2000 results.

After the scan is finished go to the specific report and call the results tab.
In my case (8 core Intel i5, 3600 bogomips each core, 16 GB RAM) the results tab needs about 45 seconds to load.

With old gvm 9 there was no noteable delay in loading results.

Additional Information

I suggest that Kali ships also the reference implementation (combination) from Greenbone Networks.

Or should it be possible to do performance optimization on the combination gvm 11 and PostgreSQL 12?




2020-10-01 18:44

reporter   ~0013518

While the query of the above example is running, these 45 seconds, there are one or partially two PostgreSQL procceses active, consuming 100 % CPU each.



2020-12-06 19:24

reporter   ~0013944

Same with GVM 20 and PostgreSQL 13.



2020-12-14 13:44

manager   ~0013977

Thanks for the report.
Unfortunately we have to use the postgresql version present in Debian Testing (currently version 13).
I don't know anything about performance optimization for postgresql / gvmd. Patches are welcome.

I hope upstream will work on this soon.



2020-12-14 18:00

reporter   ~0013981

Found this one about PostgreSQL optimization:

Found the answer to this issue in case anyone else runs across it, it’s JIT in Postgres 12.

Just edit postgresql.conf, find the commented out line that says jit = on, uncomment, change it to say jit = off, and postgres 12 works fine.



2020-12-14 19:17

reporter   ~0013982

Wonderful, the hint with jit = off helped to solve the issue, also with GVM 20 and PostgreSQL 13.



2020-12-14 20:02

reporter   ~0013983

Indeed wonderful. Not sure about the side effects of disabling JIT and if upstream can do something about it (i guess not if JIT of PostgreSQL could be responsible for this)



2020-12-21 14:55

manager   ~0013994

thanks for the hint.
I will add a note in the README.Debian of the gvm package



2022-03-28 09:15

manager   ~0015963

This report has been filed against an old version of Kali. We will be closing this ticket due to inactivity.

Please could you see if you are able to replicate this issue with the latest version of Kali Linux (

If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing, and also give information about your setup?
For more information, please read:

Issue History

Date Modified Username Field Change
2020-10-01 13:27 klbt001 New Issue
2020-10-01 13:27 klbt001 Status new => assigned
2020-10-01 13:27 klbt001 Assigned To => sbrun
2020-10-01 18:44 klbt001 Note Added: 0013518
2020-12-06 19:24 klbt001 Note Added: 0013944
2020-12-14 13:44 sbrun Note Added: 0013977
2020-12-14 13:44 sbrun Assigned To sbrun =>
2020-12-14 18:00 kali-bugreport Note Added: 0013981
2020-12-14 19:17 klbt001 Note Added: 0013982
2020-12-14 20:02 kali-bugreport Note Added: 0013983
2020-12-21 14:55 sbrun Note Added: 0013994
2021-05-31 13:37 rhertzog Category Tool Upgrade => Tool Upgrade Request
2022-03-25 13:58 g0tmi1k Severity tweak => minor
2022-03-28 09:15 daniruiz Note Added: 0015963
2022-03-28 09:15 daniruiz Assigned To => daniruiz
2022-03-28 09:15 daniruiz Status assigned => closed
2022-03-28 09:15 daniruiz Resolution open => no change required