chore(deps): bump pg-boss from 12.26.0 to 12.27.0

[dependabot]

Bumps pg-boss from 12.26.0 to 12.27.0.

Release notes

Sourced from pg-boss's releases.

12.27.0

What's Changed

This release lets schema be any name PostgreSQL accepts as a quoted identifier, fixes a set of catalog lookups that were silently wrong for schema names PostgreSQL folds to lower case, and adds a startup guard against the config mistake the new spelling makes possible.

Highlights

Quoted schema names

schema may now be passed pre-quoted to reach names that aren't legal bare identifiers — dashes, reserved words, mixed case you want preserved (#700):

new PgBoss({ schema: '"My-Schema"' })

The value is used verbatim in identifier positions, so the quotes are preserved as written. Quoting is the caller's, not pg-boss's: MySchema and "MySchema" are different schemas, since PostgreSQL folds the unquoted form to myschema. Existing configurations are unaffected — a bare name emits exactly the SQL it does today.

Inside a quoted name, double quotes, single quotes, percent signs, periods, dollar signs, backslashes and control characters are rejected. Each one would either escape the identifier or corrupt the format() / dollar-quoted bodies the schema is interpolated into.

Thanks to @​MoazEmad1 for the original PR (#859).

Catalog lookups now use the resolved schema name

PostgreSQL stores the folded name, so every nspname = '<schema>' comparison pg-boss makes had to fold too. It didn't. With a mixed-case bare name such as schema: 'MySchema' (accepted by every prior version, stored by PostgreSQL as myschema), each of these was silently broken:

• Queue stats partition maintenance — the "does today's partition exist" check never matched, so maintenance re-issued CREATE TABLE … PARTITION OF on a partition that already existed and failed with relation already exists. Retention pruning found no partitions to drop, so old ones accumulated forever.
• detectSchemaDrift() / pg-boss doctor — reported an entirely empty schema, i.e. every table, index, function, column, constraint and enum value as missing.
• BAM background index builds — the liveness probe and the invalid-index heal probe both resolved to nothing, so a stalled build was reclaimed on timeout only and an invalid leftover index was never healed.

All of these now resolve the configured value to the name in pg_namespace before comparing.

The notify channel and advisory lock key are deliberately not folded. They're hashes of a string, never compared against the catalog, so they only need to agree between instances — and folding them would change the channel and lock key of every existing bare name, leaving old and new instances unable to coordinate during a rolling upgrade. Only redundant quoting is collapsed ('"pgboss"' and 'pgboss' land on one channel). Derived values stay byte-identical to prior releases.

Guardrails for the two spellings

MySchema and "MySchema" differ by two characters in config, name two different schemas, and look identical in logs. Mis-spelling the quoting was not an error on its own: pg-boss found no installation, created an empty second schema, and every existing job appeared to have vanished. start() now refuses to install into a schema when another one differing from it only by case already holds a pg-boss installation, and names the spelling that reaches the existing data:

pg-boss is not installed in schema MySchema, but is installed in "MySchema", which differs only
in case. PostgreSQL folds unquoted names to lower case and stores quoted names verbatim, so these
are different schemas. To use the existing installation, set schema: '"MySchema"'. To install a
new schema beside it anyway, set allowSchemaCaseVariant: true.

Only pg-boss installations count, so an unrelated schema that happens to share a folded name never blocks an install. The check runs once, on the install path only. Set the new allowSchemaCaseVariant option to true if two installations whose names differ by case are genuinely intended.

Relatedly, the error for a name that isn't a legal bare identifier now hands back the config that works, instead of only naming the rule that was broken:

Schema name "my-schema" can only contain alphanumeric characters or underscores when unquoted.
Pass it quoted to use it verbatim: schema: '"my-schema"'
</tr></table> 

... (truncated)

Commits

• aa1ce16 fix flaky test
• 617ec33 added tests
• d034e75 new config option to allow schema case variants on startup
• feb0d76 deps and versioning
• 69e33eb updates for schema quoting PR
• 0148543 Merge pull request #859 from MoazEmad1/schema-identifier-quoting
• 0ce5d27 docs domain update
• faaa887 update vitepress
• 6022c02 allow caller-quoted schema names
• f869cc9 deps and versioning for dashboard
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)