Skip to content

Conversation

@jchancojr
Copy link
Contributor

What kind of change does this PR introduce?

Feature- pgBackRest backup solution

What is the current behavior?

pgBackRest tasks and configs are absent

What is the new behavior?

pgBackRest tasks and configs are missing are present

Additional context

NA

@jchancojr jchancojr self-assigned this Oct 29, 2025
@jchancojr jchancojr added the enhancement New feature or request label Oct 29, 2025
* origin/PSQL-773:
  fix(setup-pgbackrest.yml): errant indentation fix
  fix(setup-pgbackrest.yml): fix file module
  fix(setup-pgbackrest.yml): update nix install path
  feat(ansible): add pgBackRest tasks and configurations
jchancojr and others added 6 commits October 30, 2025 10:57
The pgbackrest wrapper script now sanitizes arguments passed to it.
This change removes potentially sensitive or command-injection-vulnerable arguments such as `--cmd`, `--repo-host-cmd`, and `--config` before executing the pgbackrest command. This enhances security by preventing accidental exposure of sensitive information.
jchancojr and others added 5 commits November 14, 2025 11:13
@jchancojr jchancojr requested a review from hunleyd November 14, 2025 17:11
@hunleyd hunleyd self-requested a review November 14, 2025 18:12
@hunleyd hunleyd self-requested a review November 14, 2025 20:32
cuongdo added a commit to cuongdo/multigres that referenced this pull request Nov 14, 2025
follow up for:
multigres#226 (comment)

Also added some of the configs from the Supabase pgBackRest config
supabase/postgres#1878

Signed-off-by: Cuong Do <cuongdo@users.noreply.github.com>
cuongdo added a commit to multigres/multigres that referenced this pull request Nov 17, 2025
* fix(multipooler): read cached copy of pooler topo

follow up for:
#226 (comment)

Also added some of the configs from the Supabase pgBackRest config
supabase/postgres#1878

Signed-off-by: Cuong Do <cuongdo@users.noreply.github.com>

* Remove "Cached" from state getter functions

Signed-off-by: Cuong Do <cuongdo@users.noreply.github.com>

* Make restore more resilient to stale PG conns

Restore wasn't handling the dead DB connections left behind by its
stopping/restarting Postgres. However, this raises the question of how
resilient multipooler.Executor needs to be in this situation.

Signed-off-by: Cuong Do <cuongdo@users.noreply.github.com>

* do not start postgres if restore fails

orch should detect this and initiate fix

Signed-off-by: Cuong Do <cuongdo@users.noreply.github.com>

---------

Signed-off-by: Cuong Do <cuongdo@users.noreply.github.com>
@jchancojr
Copy link
Contributor Author

Tested local infra with workflow ami:
✅ pause
✅ resume
✅ upgrades

MesuterPikin added a commit to MesuterPikin/multigres that referenced this pull request Nov 29, 2025
* fix(multipooler): read cached copy of pooler topo

follow up for:
multigres/multigres#226 (comment)

Also added some of the configs from the Supabase pgBackRest config
supabase/postgres#1878

Signed-off-by: Cuong Do <cuongdo@users.noreply.github.com>

* Remove "Cached" from state getter functions

Signed-off-by: Cuong Do <cuongdo@users.noreply.github.com>

* Make restore more resilient to stale PG conns

Restore wasn't handling the dead DB connections left behind by its
stopping/restarting Postgres. However, this raises the question of how
resilient multipooler.Executor needs to be in this situation.

Signed-off-by: Cuong Do <cuongdo@users.noreply.github.com>

* do not start postgres if restore fails

orch should detect this and initiate fix

Signed-off-by: Cuong Do <cuongdo@users.noreply.github.com>

---------

Signed-off-by: Cuong Do <cuongdo@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants