Skip to content

Update doc for VALKEYMODULE_OPTIONS_HANDLE_FORKLESS - #474

Open
JimB123 wants to merge 1 commit into
valkey-io:mainfrom
JimB123:forkless-option
Open

Update doc for VALKEYMODULE_OPTIONS_HANDLE_FORKLESS#474
JimB123 wants to merge 1 commit into
valkey-io:mainfrom
JimB123:forkless-option

Conversation

@JimB123

@JimB123 JimB123 commented Aug 25, 2026

Copy link
Copy Markdown
Member

Add new module flag: VALKEYMODULE_OPTIONS_HANDLE_FORKLESS

Update description for ValkeyModule_OpenKey()

@JimB123
JimB123 requested a review from murphyjacob4 August 25, 2026 22:12
Signed-off-by: Jim Brunner <brunnerj@amazon.com>
@JimB123
JimB123 requested a review from nitaicaro August 25, 2026 22:25
Comment thread topics/modules-api-ref.md
This requires that:
* If the module defines a new type, the `rdb_save` function must be thread-safe.
* If the module defines an `aux_save`/`aux_save2` function, the function must run only in the
`VALKEYMODULE_AUX_BEFORE_RDB` section of the RDB and the function must export only limited data (as

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

VALKEYMODULE_AUX_BEFORE_RDB

Is this a formal requirement? I don't remember us enforcing this anywhere. Should we enforce this at load time? Or is there still a valid case for AFTER_RDB?

@madolson

madolson commented Sep 1, 2026

Copy link
Copy Markdown
Member

@JimB123 This file is programmatically generated from module.c documentation, you should make changes there and they get updated when we do releases.

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