Commit 47076dc
Only Delete Backup pgtask if One Already Exists
When cleaning the existing backup pgtask Custom Resource prior to
creating a new backup for a cluster, the PostgreSQL Operator will now
only attempt to delete a prior backup pgtask if one currently exists.
This ensures that certain backups can be properly submitted and
executed in the event that the pgtask from the previous cluster backup
has been removed (either manually or by the Operator). For instance,
this ensures that the post-restore backup executed following a cluster
restore can still be executed in the event that the user has scaled
down the cluster prior to the restore, since successfully scaling down
a replica currently results in the deletion of all pgtasks for the
specific cluster.1 parent 4b48932 commit 47076dc
1 file changed
+16
-11
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
225 | 225 | | |
226 | 226 | | |
227 | 227 | | |
228 | | - | |
229 | 228 | | |
230 | | - | |
231 | | - | |
232 | | - | |
233 | | - | |
234 | | - | |
| 229 | + | |
| 230 | + | |
| 231 | + | |
235 | 232 | | |
236 | 233 | | |
237 | 234 | | |
238 | 235 | | |
239 | | - | |
240 | | - | |
241 | | - | |
242 | | - | |
243 | | - | |
| 236 | + | |
| 237 | + | |
| 238 | + | |
| 239 | + | |
| 240 | + | |
| 241 | + | |
| 242 | + | |
| 243 | + | |
| 244 | + | |
| 245 | + | |
| 246 | + | |
| 247 | + | |
| 248 | + | |
244 | 249 | | |
245 | 250 | | |
246 | 251 | | |
| |||
0 commit comments