pg_catalog: fix up contents of pg_catalog.pg_proc
#123651
Labels
A-sql-pgcompat
Semantic compatibility with PostgreSQL
C-cleanup
Tech debt, refactors, loose ends, etc. Solution not expected to significantly change behavior.
O-pg-regress
Originated from the pg_regress test suite.
T-sql-foundations
SQL Foundations Team (formerly SQL Schema + SQL Sessions)
T-sql-queries
SQL Queries Team
Comments
yuzefovich
added
C-cleanup
craig bot
pushed a commit
that referenced
this issue
May 6, 2024
123652: roachtest: skip opr_sanity.sql in pg_regress r=yuzefovich a=yuzefovich We currently have incomplete `pg_catalog.pg_proc` contents, so `opr_sanity.sql` subtest results in invalid entries that need to be updated every time when a new builtin function is introduced, which is an unnecessary toil. Let's skip this subtest for now. Informs: #123401. Informs: #123651. Epic: None Release note: None Co-authored-by: Yahor Yuzefovich <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, when running
opr_sanity.sqlsubtest ofpg_regresstest suite, we get lots of rows on queries that should be returning none, indicating that some illegal values / incomplete information is present. For now, in order to avoid unnecessary churn of the pg_regress diff file when adding new builtins, we'll skipopr_sanity.sqlaltogether.Jira issue: CRDB-38448
The text was updated successfully, but these errors were encountered: