Skip to content

🔄 Sync with upstream changes#17

Open
h0lybyte wants to merge 506 commits into
mainfrom
upstream-main
Open

🔄 Sync with upstream changes#17
h0lybyte wants to merge 506 commits into
mainfrom
upstream-main

Conversation

@h0lybyte

Copy link
Copy Markdown
Member

Upstream Sync

This PR contains the latest changes from the upstream repository.

Changes included:

  • Synced from upstream/main
  • Auto-generated by upstream sync workflow

Review checklist:

  • Review the changes for any breaking changes
  • Check for conflicts with local modifications
  • Verify tests pass (if applicable)

This PR was automatically created by the upstream sync workflow

semantic-release-bot and others added 30 commits March 27, 2026 00:55
Co-authored-by: supabase-workflow-trigger[bot] <266661614+supabase-workflow-trigger[bot]@users.noreply.github.com>
Co-authored-by: supabase-workflow-trigger[bot] <266661614+supabase-workflow-trigger[bot]@users.noreply.github.com>
* Application.fetch_env! does an ETS lock on every single read and we do it across several high volume areas of the service
* Map.drop removed as Jason already tackles this and this will prevent map copy
* Always use gen_rpc as the communication method between cluster
with push metrics available this code is no longer required and adds bloat to the system
Emit telemetry errors on all log errors
…upabase#1787)

* fix: ensure RateCounter avg is always per second
* fix: change tenant rate counters to tick every 5 seconds
Co-authored-by: supabase-workflow-trigger[bot] <266661614+supabase-workflow-trigger[bot]@users.noreply.github.com>
filipecabaco and others added 30 commits June 10, 2026 11:23
* chore: update @supabase/supabase-js to v2.108.2

* chore: update nix node_modules hash

---------

Co-authored-by: supabase-workflow-trigger[bot] <266661614+supabase-workflow-trigger[bot]@users.noreply.github.com>
Co-authored-by: supabase-autofix-bot <noreply@supabase.com>
To support the recommended client-id
Instead of always deleting the subscriptions table when
SubscriptionManager starts we:

* warm restarts now re-adopt ETS and re-monitor subscribers
* cold start cleans up the DB

Orphan processes are not a problem because ReplicationPoller simply
broadcasts if it can't find the pid related to the subscription row
Increase default ReplicationConnection timeout from 30 seconds to 4 minutes to give more times for really busy databases to establish a replication slot.

Also move creating the replication slot to happen after the publication is there.
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.

10 participants