Skip to content

Sync from docs: PSYNC_S2305 covers two bucket limits, add self-hosted config (powersync-docs #587) - #82

Merged
michaelbarnes merged 1 commit into
mainfrom
drift/docs-587-bucket-count-limits
Aug 26, 2026
Merged

Sync from docs: PSYNC_S2305 covers two bucket limits, add self-hosted config (powersync-docs #587)#82
michaelbarnes merged 1 commit into
mainfrom
drift/docs-587-bucket-count-limits

Conversation

@bean1352

Copy link
Copy Markdown
Collaborator

Generated by Claude. Review carefully before merging.

Source docs PR: powersync-ja/powersync-docs#587

What changed in docs

Docs PR #587 added two new pages (Bucket Count and Limits, Reducing Bucket Count) and clarified that PSYNC_S2305 covers two distinct per-user limits, not just one: unique bucket count and parameter query results, both defaulting to 1,000. It also documented new api.parameters config keys for self-hosted deployments to raise those limits.

Skill updates in this PR

  • skills/powersync/references/sync-config.md: Updated the "Bucket limits" callout in the Structure section to mention both per-user limits (unique bucket count and parameter lookup rows), note that exceeding either raises PSYNC_S2305, and link to the new Bucket Count docs page.
  • skills/powersync/references/powersync-debug.md: Added PSYNC_S2305 to the key error codes table with guidance to read the error message to distinguish which limit was reached. Updated the Common Causes "Too many buckets" entry to mention both limits and link to the new Reducing Bucket Count page.
  • skills/powersync/references/powersync-service.md: Added a new "Per-User Sync Limits" subsection under Service Configuration (Self-hosted) documenting the api.parameters.max_buckets_per_connection and api.parameters.max_parameter_query_results keys in service.yaml, with a note to set both and a link to the reduction guide.

Notes for reviewer

The two limits measure different things and can diverge: a user can fail the parameter query results limit while their unique bucket count is still well under 1,000 (for example, if a CTE returns 1,200 org IDs but those collapse into fewer unique buckets after deduplication). The error message text is the reliable signal for which limit was hit, so the skill edits emphasize reading the message before choosing a fix.

The PSYNC_S1601 action in powersync-debug.md still reflects the old guidance (re-enable CDC, replication resumes automatically). PR #76 (open) updates that row and adds further MSSQL error codes. No conflict between these two PRs: they touch the same table but different rows.

No new skill file was created. The new docs pages (bucket-count, reducing-bucket-count) are reference material for developers; the agent-usable rules fit cleanly into the three existing files.


Generated by Claude Code

…rs config

- sync-config.md: update bucket limit note to mention both per-user limits
  (unique bucket count and parameter query results, each defaulting to 1,000)
- powersync-debug.md: add PSYNC_S2305 to error codes table; update the
  common causes entry to distinguish the two limits and link to reducing guide
- powersync-service.md: add Per-User Sync Limits section documenting the
  api.parameters config block for raising limits on self-hosted deployments

Docs source: powersync-ja/powersync-docs#587

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TCXCVHmByERZzvc4CCbLM3
@bean1352
bean1352 requested a review from michaelbarnes August 26, 2026 11:35
@bean1352 bean1352 self-assigned this Aug 26, 2026
@michaelbarnes
michaelbarnes merged commit 783d0da into main Aug 26, 2026
1 check passed
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.

3 participants