Skip to content

fix: Postgres query on non-existent column throws internal server error #1689

fix: Postgres query on non-existent column throws internal server error

fix: Postgres query on non-existent column throws internal server error #1689

Triggered via pull request March 24, 2026 23:34
Status Success
Total duration 16m 59s
Artifacts 3

ci-performance.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

1 warning
Benchmarks
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
baseline-benchmark Expired
3.56 KB
sha256:80635100274234d4109e850b0c040d3a13cec604a5ddc7a03e1e98770b10780c
benchmark-comparison Expired
596 Bytes
sha256:9453d190474576d77a13de2d68179fbba35c4df6bc6205faec5a7eff64be5baa
pr-benchmark Expired
3.51 KB
sha256:bab58c7e5c7786bff376c9e511674506ba0a8cd36c902ed29eaf677963d50ea1