Skip to content

test: cover #20/#21 partition-key UPDATE rejection (no _events leak)#24

Merged
vyruss merged 1 commit into
mainfrom
test/cover-issue-20-21-partition-key
Jun 19, 2026
Merged

test: cover #20/#21 partition-key UPDATE rejection (no _events leak)#24
vyruss merged 1 commit into
mainfrom
test/cover-issue-20-21-partition-key

Conversation

@vyruss

@vyruss vyruss commented Jun 19, 2026

Copy link
Copy Markdown
Collaborator

#21 (hot row cross-tier ts update leaks the internal _events name) has the same root cause as #20 and is already fixed by partition-column block in #23. UPDATE is rejected at parse-analyze before the hot DML that hits PG partition router. Adds CI journey assertions for both directions plus explicit check that _events never appears in the error. Closes #21.

@coderabbitai

coderabbitai Bot commented Jun 19, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@vyruss, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 40 minutes and 27 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 06e0b048-90ef-47cf-aab2-3ce06441ecd5

📥 Commits

Reviewing files that changed from the base of the PR and between 4f5f679 and 80890cd.

📒 Files selected for processing (1)
  • ci/journey.sh
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch test/cover-issue-20-21-partition-key

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@vyruss vyruss merged commit 905c77c into main Jun 19, 2026
6 checks passed
@vyruss vyruss deleted the test/cover-issue-20-21-partition-key branch June 19, 2026 19:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

UPDATE of hot row's partition key to archived ts range leaks internal _events table name

1 participant