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.

Sign up for GitHub

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

Jump to bottom

chore: archive - move error to trace level when insert row fails #2283

Merged
merged 2 commits into from
Dec 15, 2023
Merged

chore: archive - move error to trace level when insert row fails #2283

merged 2 commits into from
Dec 15, 2023

Commits on Dec 12, 2023

  1. archive: move error to trace level when insert row fails 

    That is helpful to prevent the node to spam the logs when it shares
connection to the same Postgres database with other nodes, in
which case the following log appears too much:

topics="waku archive" tid=1 file=archive.nim:113 err="error in
runStmt: error in dbConnQueryPrepared calling waitQueryToFinish: error
in query: ERROR: duplicate key value violates unique constraint
"messageindex" DETAIL: Key
(messagehash)=(88f4ee115eef6f233a7dceaf975f03946e18666adda877e38d61be98add934e8)
already exists. "
    @Ivansete-status
    Ivansete-status committed Dec 12, 2023
    Configuration menu
    Copy the full SHA
    8489930 View commit details
    Browse the repository at this point in the history

Commits on Dec 15, 2023

  1. archive.nim: only move to trace the log of duplicate key 

    This condition happens when multiple nodes share the same database
    @Ivansete-status
    Ivansete-status committed Dec 15, 2023
    Configuration menu
    Copy the full SHA
    d0c8bd7 View commit details
    Browse the repository at this point in the history