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.
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
fix: disable WAL archiving during import bootstrap #3743
Conversation
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
❗ By default, the pull request is configured to backport to all release branches.
|
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
E2E test on EDB fork https://github.com/EnterpriseDB/cloudnative-pg/actions/runs/7697496524 |
Rerun E2E tests after fixing wal senders GUC. See https://github.com/EnterpriseDB/cloudnative-pg/actions/runs/7699971017 |
Run E2E tests on EDB account: https://github.com/EnterpriseDB/cloudnative-pg/actions/runs/7709440784 |
When using the import facility of the initdb bootstrap method in a job, optimize the PostgreSQL instance for the sole duration of the job, by setting the following GUCs: - `archive_mode` to `off` - `fsync` to `off` - `full_page_writes` to `off` - `wal_level` to `minimal` Then, restore the configuration and invoke `initdb --sync-only` before the end of the import job. Closes #3741 Signed-off-by: Gabriele Bartolini <gabriele.bartolini@enterprisedb.com>
Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com>
Signed-off-by: Gabriele Bartolini <gabriele.bartolini@enterprisedb.com>
Signed-off-by: Gabriele Bartolini <gabriele.bartolini@enterprisedb.com>
Signed-off-by: Gabriele Bartolini <gabriele.bartolini@enterprisedb.com>
Signed-off-by: Gabriele Bartolini <gabriele.bartolini@enterprisedb.com>
Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com>
Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com>
/ok-to-merge |
When using the import facility of the initdb bootstrap method in a job, optimize the PostgreSQL instance for the sole duration of the job by setting the following GUCs: - `archive_mode` to `off` - `fsync` to `off` - `full_page_writes` to `off` - `max_wal_senders` to `0` - `wal_level` to `minimal` Then, restore the configuration and invoke `initdb --sync-only` before the end of the import job. This avoids unnecessary and systematic piling of WAL files during any import job. Closes #3741 Signed-off-by: Gabriele Bartolini <gabriele.bartolini@enterprisedb.com> Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com> Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> Co-authored-by: Armando Ruocco <armando.ruocco@enterprisedb.com> Co-authored-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> (cherry picked from commit 9e58cbd)
When using the import facility of the initdb bootstrap method in a job, optimize the PostgreSQL instance for the sole duration of the job by setting the following GUCs: - `archive_mode` to `off` - `fsync` to `off` - `full_page_writes` to `off` - `max_wal_senders` to `0` - `wal_level` to `minimal` Then, restore the configuration and invoke `initdb --sync-only` before the end of the import job. This avoids unnecessary and systematic piling of WAL files during any import job. Closes #3741 Signed-off-by: Gabriele Bartolini <gabriele.bartolini@enterprisedb.com> Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com> Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> Co-authored-by: Armando Ruocco <armando.ruocco@enterprisedb.com> Co-authored-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> (cherry picked from commit 9e58cbd)
When using the import facility of the initdb bootstrap method in a job, optimize the PostgreSQL instance for the sole duration of the job by setting the following GUCs: - `archive_mode` to `off` - `fsync` to `off` - `full_page_writes` to `off` - `max_wal_senders` to `0` - `wal_level` to `minimal` Then, restore the configuration and invoke `initdb --sync-only` before the end of the import job. This avoids unnecessary and systematic piling of WAL files during any import job. Closes #3741 Signed-off-by: Gabriele Bartolini <gabriele.bartolini@enterprisedb.com> Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com> Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> Co-authored-by: Armando Ruocco <armando.ruocco@enterprisedb.com> Co-authored-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> (cherry picked from commit 9e58cbd)
When using the import facility of the initdb bootstrap method in a job, optimize the PostgreSQL instance for the sole duration of the job by setting the following GUCs: - `archive_mode` to `off` - `fsync` to `off` - `full_page_writes` to `off` - `max_wal_senders` to `0` - `wal_level` to `minimal` Then, restore the configuration and invoke `initdb --sync-only` before the end of the import job. This avoids unnecessary and systematic piling of WAL files during any import job. Closes #3741 Signed-off-by: Gabriele Bartolini <gabriele.bartolini@enterprisedb.com> Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com> Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> Co-authored-by: Armando Ruocco <armando.ruocco@enterprisedb.com> Co-authored-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com>
When using the import facility of the initdb bootstrap method in a job, optimize the PostgreSQL instance for the sole duration of the job, by setting the following GUCs:
archive_mode
tooff
fsync
tooff
full_page_writes
tooff
max_wal_senders
to0
wal_level
tominimal
Then, restore the configuration and invoke
initdb --sync-only
before the end of the import job.This avoids unnecessary and systematic piling of WAL files during any import job.
Closes #3741