Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add vt_refs table #570

Merged
merged 6 commits into from
Jun 4, 2019
Merged

Conversation

janowagner
Copy link
Member

The table "vt_refs" is created and when a next VT update is running, the table will be filled with the references of the VTs.

In total currently about 370K entries should appear in the table.
A subsequent feed update takes about 4-5 minutes and there is a additional log entry to follow this activity more easily.

The content of the vt_refs table is not used yet. The same information redundantly is still in the nvts table. Switching over to using the vt_refs and removing the redundant data in nvts is subject to subsequent pull requests.

The new table and index is only implemented for PostgreSQL. SQLite3-based setups will fail during run time.

@janowagner janowagner requested a review from a team May 29, 2019 13:04
src/manage_pg.c Outdated Show resolved Hide resolved
src/manage_sql_nvts.c Outdated Show resolved Hide resolved
src/manage_sql_nvts.c Show resolved Hide resolved
src/manage_sql_nvts.c Show resolved Hide resolved
This happens additional to the respective
fields cve, xref, bid in table nvts for the time being.
Add a regular log entry once a newer feed uis detected
via OSP. Phrase the log entry about finished update a bit clearer.
@mattmundell mattmundell merged commit 4e6ca40 into greenbone:master Jun 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants