questdb / questdb/questdb

Enable ALTER TABLE name SUSPEND WAL; without entering dev mode

Open
#6,236 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

New feature
Dominant language
Java
Stars
17.3k
Forks
1.6k
Avg merge
5d 10h
Merged PRs (30d)
28

Description

Is your feature request related to a problem?

Currently, if we need to skip a slow transaction, we run:

enable dev mode (dev.mode.enabled=true)
disable WAL apply
restart
alter table suspend wal and then alter table resume wal from txn
revert the config (dev.mode.enabled=false)
another restart

Describe the solution you'd like.

Consider making dev.mode.enable a reloadable param or implement a different way to execute alter table suspend wal avoiding the dev mode completely.

Describe alternatives you've considered.

No response

Full Name:

Anna

Affiliation:

QuestDB

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how ALTER TABLE SUSPEND WAL is handled and how the dev.mode.enabled configuration gates it. The issue names no files or tests; done should allow the command without enabling dev mode, configuration changes, or restarts, while preserving ALTER TABLE RESUME WAL FROM TXN behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, sql
Domain
databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.