Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

missing initdb panic handler #527

Open
pmp-p opened this issue Feb 6, 2025 · 0 comments
Open

missing initdb panic handler #527

pmp-p opened this issue Feb 6, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@pmp-p
Copy link
Collaborator

pmp-p commented Feb 6, 2025 •
edited
Loading

Since we are about to integrate configuration changes from user that may happen right after initdb but without real validation, any persistent filesystem could get corrupted by wrong or missing configuration files.

We need to handle any abort() at initdb stage and be able to clear data folder so the process can start again after fixing conditions.

Image

Actually it would eg require to go in javascript tools from browser and manually delete the indexed database.

related #415
@pmp-p pmp-p added the enhancement New feature or request label Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pmp-p