github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-23 07:18:56 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[PR #4798] [MERGED] docs: supabase migration for large number of rows #22482

New Issue
Closed
opened 2026-04-15 21:04:43 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-15 21:04:43 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/4798
Author: @Kinfe123
Created: 9/21/2025
Status: ✅ Merged
Merged: 11/20/2025
Merged by: @himself65

Base: canary ← Head: docs/supabase-migration-for-large-rows

📝 Commits (3)

  • ca6cc73 docs: supabase migration for large number of rows
  • a9663f4 Merge branch 'canary' into docs/supabase-migration-for-large-rows
  • f98719a Merge branch 'canary' into docs/supabase-migration-for-large-rows

📊 Changes

1 file changed (+4 additions, -0 deletions)

View changed files

📝 docs/content/docs/guides/supabase-migration-guide.mdx (+4 -0)

📄 Description

this is draft still since i cant able to seed that many user (~7mil) but i was able to do upto 300k seeding but it seems to be working but this is my researched guess on moving the js logic to pg level query logic to make the offset and steaming works correctly. since the object that created at js level would leads to OOM issue leaving GC is not collecting it

Summary by cubic

Add a warning callout to the Supabase migration guide for large datasets (100k+ users) to prevent OOM during migrations. It recommends streaming or keyset pagination, processing 1k-row batches with concurrency 8, and a temporary Node memory increase.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/better-auth/better-auth/pull/4798 **Author:** [@Kinfe123](https://github.com/Kinfe123) **Created:** 9/21/2025 **Status:** ✅ Merged **Merged:** 11/20/2025 **Merged by:** [@himself65](https://github.com/himself65) **Base:** `canary` ← **Head:** `docs/supabase-migration-for-large-rows` --- ### 📝 Commits (3) - [`ca6cc73`](https://github.com/better-auth/better-auth/commit/ca6cc737eca0a8a578846e9cf9edb092123c30ae) docs: supabase migration for large number of rows - [`a9663f4`](https://github.com/better-auth/better-auth/commit/a9663f4a7384a37ad263736f0722ff5a89c368fd) Merge branch 'canary' into docs/supabase-migration-for-large-rows - [`f98719a`](https://github.com/better-auth/better-auth/commit/f98719aa49b3278919ec98fd9d34adf297342018) Merge branch 'canary' into docs/supabase-migration-for-large-rows ### 📊 Changes **1 file changed** (+4 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `docs/content/docs/guides/supabase-migration-guide.mdx` (+4 -0) </details> ### 📄 Description this is draft still since i cant able to seed that many user (~7mil) but i was able to do upto 300k seeding but it seems to be working but this is my researched guess on moving the js logic to pg level query logic to make the offset and steaming works correctly. since the object that created at js level would leads to OOM issue leaving GC is not collecting it <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Add a warning callout to the Supabase migration guide for large datasets (100k+ users) to prevent OOM during migrations. It recommends streaming or keyset pagination, processing 1k-row batches with concurrency 8, and a temporary Node memory increase. <!-- End of auto-generated description by cubic. --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-15 21:04:43 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#22482
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?