Push leaves 61 extra tables on the host (56 `__wp_*` copies and 5 `wp_sqm_*`)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
Research direction
Start by reproducing the push with wp db tables --all-tables and the provided grep command, then trace the CLI database import path responsible for renamed tables. Done means successful imports do not leave rollback or unexplained tables, or the CLI clearly reports why they remain; verify the final table counts and summary output.
Written by the indexing model from the issue text.
Description
Quick summary
After a successful studio push, the Pressable database had 115 tables where the pushed site has 59. 56 were renamed __wp_* copies of the pre-push tables and 5 were wp_sqm_* tables.
Steps to reproduce
- Same setup as the companion issue on wp-config.php replacement.
wp db tables --all-tables | wc -lbefore and after the push on the host.wp db tables --all-tables | grep -E '^(__wp_|wp_sqm_)'.
What you expected to happen
The database ends as pushed. Any tables the importer renames for rollback are dropped when the import completes, or the CLI says they were kept and why.
What actually happened
Content and options matched the pushed site, but 56 __wp_* and 5 wp_sqm_* tables remained. Nothing in the CLI output mentioned them.
App or CLI? CLI
Version wp-studio@1.21.0
Impact Roughly doubles the host database size for a site of this shape. On hosts that bill or limit by database size, or that back up the whole database, that cost persists until someone notices.
Workarounds Drop the __wp_* tables by hand after confirming the import. We did not identify what wp_sqm_* belongs to, so we left those.
Platform Pressable (staging site)
Architecture macOS 26.6.2, arm64
Logs or notes
- Table counts: 59 pushed, 115 on host after push.
- Asks: drop the
__wp_*set on import success; explain or removewp_sqm_*; report leftover tables in the CLI summary.
Site ID and the local Studio site are available privately on request; they are omitted here because the target is a client site.
- Dominant language
- TypeScript
- Stars
- 523
- Forks
- 99
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 167
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Automattic/studio
-
Enhancement Quality Sprint: Week 2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Automattic/studio#4683 ·
-
[Status] Auto-allocated Bug YOLO
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Automattic/studio#3386 · 1 comment ·
-
Enhancement
Difficulty 1/5 Under an hour Newbie friendliness 75/100
Automattic/studio#3017 · 4 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Automattic/studio#2868 · 2 comments ·
-
unable to log in Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Automattic/studio#4898 ·
All issues in Automattic/studio
Similar issues
-
comp/dashboard P3 type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
NousResearch/hermes-agent#117722 ·
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·