feat: add InitializeSchema option to delayed requeuer publisher and subscriber configs#57
Merged
m110 merged 3 commits intoThreeDotsLabs:masterfrom Mar 23, 2026
Conversation
…figs This allows disabling automatic schema initialization for environments where the database user doesn't have CREATE TABLE permissions.
m110
approved these changes
Mar 23, 2026
m110
approved these changes
Mar 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation / Background
Currently, the delayed publisher/subscriber for both PostgreSQL and MySQL always attempts to automatically initialize the database schema (CREATE TABLE). This causes issues in production environments where the database user has restricted permissions and cannot create tables.
This change adds an InitializeSchema configuration option that allows users to disable automatic schema initialization when needed.
Details
Added InitializeSchema field to:
Changed hardcoded
AutoInitializeSchema: true / InitializeSchema: trueto use the config value insteadThe option is propagated through the requeuer to its internal publisher and subscriber
Alternative approaches considered (if applicable)
Alternative approach could be to change name from
InitializeSchematoDisableInitializeSchemato be backwards compatible if someone currently depends on auto initialize.I used
InitializeSchemato be consistent with naming in other files.Checklist
The resources of our team are limited. There are a couple of things that you can do to help us merge your PR faster:
make up.make test_shortfor a quick check.make test.