1
47%
main: 65%

Ran 28 Jan 2025 08:57PM UTC

Files 58

Run time 3s

Badge

Embed ▾

Committed 28 Jan 2025 08:52PM UTC coverage: 46.37% (+12.2%) from 34.148%

Job # b77d19ae3552e72f2f1980e2643843c353e729d0-PR-580.1

Build Type

Pull #580

github

Committed by

hauleth

Commit Message

fix: more correct name validation

PostgreSQL requires that the DB name is a valid identifier

https://www.postgresql.org/docs/current/sql-syntax-lexical.html#SQL-SYNTAX-IDENTIFIERS

This was causing some issues with metrics gathering in the past, but
that should be resolved now. This makes it more in-line with what
PostgreSQL is allowing and expecting. The max length is compile-time
configurable, as PostgreSQL technically provides a way to increase the
byte limit, by default we use current PostgreSQL default there.

This mean that some users *may* be allowed to use weird names, but
assuming that Victoria Metrics is properly parsing exported metrics
using OpenMetrics specs, then it should work there.

Close #579

Pull Request Pull Request #580: fix: more correct DB name handling

Run Details

907 of 1956 relevant lines covered (46.37%)

75.46 hits per line

supabase / supavisor / b77d19ae3552e72f2f1980e2643843c353e729d0-PR-580 / 1
47%
main: 65%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job b77d19ae3552e72f2f1980e2643843c353e729d0-PR-580.1

supabase / supavisor / b77d19ae3552e72f2f1980e2643843c353e729d0-PR-580 / 1 47% main: 65%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job b77d19ae3552e72f2f1980e2643843c353e729d0-PR-580.1

supabase / supavisor / b77d19ae3552e72f2f1980e2643843c353e729d0-PR-580 / 1
47%
main: 65%

README BADGES
x