pg_dumpall: unrecognized option '--if-exists' #497

New Issue

Closed

opened 2022-02-09 04:01:34 +00:00 by Firesphere · 4 comments

Firesphere commented 2022-02-09 04:01:34 +00:00

Copy Link

What I'm trying to do and why

Include Postgres 9.2 dumps in the backup, because databases are important.

Steps to reproduce (if a bug)

Attempt to backup a system with a Postgres hook, on Postgres <10

Actual behavior (if a bug)

Postgres shows an error that --if-exists is not a valid command.
This is due to the PG on this server is older (9.x), which I sadly can't do anything about.

Expected behavior (if a bug)

Actually dump out a database

Other notes / implementation ideas

Environment

borgmatic version: [version here]

1.5.22

borgmatic installation method: [e.g., Debian package, Docker container, etc.]

Pip3

Borg version: [version here]

Borg 1.1.17

Python version: [version here]

python 3.6.8

Database version (if applicable): [version here]

pg_dumpall (PostgreSQL) 9.2.24

operating system and version: [OS here]
CentOS 7

### What I'm trying to do and why Include Postgres 9.2 dumps in the backup, because databases are important. #### Steps to reproduce (if a bug) Attempt to backup a system with a Postgres hook, on Postgres <10 #### Actual behavior (if a bug) Postgres shows an error that --if-exists is not a valid command. This is due to the PG on this server is older (9.x), which I sadly can't do anything about. #### Expected behavior (if a bug) Actually dump out a database #### Other notes / implementation ideas #### Environment **borgmatic version:** [version here] 1.5.22 **borgmatic installation method:** [e.g., Debian package, Docker container, etc.] Pip3 **Borg version:** [version here] Borg 1.1.17 **Python version:** [version here] python 3.6.8 **Database version (if applicable):** [version here] pg_dumpall (PostgreSQL) 9.2.24 **operating system and version:** [OS here] CentOS 7

witten commented 2022-02-09 05:12:44 +00:00

Owner

Copy Link

I'm really sorry, but that version of PostgreSQL is no longer supported by the PostgreSQL organization, and so isn't supported by borgmatic's database hooks. I admit that this limitation could be documented better. In general, borgmatic "officially" supports software that is actively supported by its maintainers, as this small volunteer effort has limited time. For instance, borgmatic just dropped support for Python 3.6, which was recently end-of-lifed.

As a work-around, if you still want to use borgmatic, you could manually dump the database with a before_backup hook into a location specified in your source_directories so that the dump will be included in each backup. However, that wouldn't make use of any of borgmatic's built-in database dump or restore functionality.

Thanks for your understanding.

I'm really sorry, but that version of PostgreSQL is no longer [supported by the PostgreSQL organization](https://www.postgresql.org/support/versioning/), and so isn't supported by borgmatic's database hooks. I admit that this limitation could be documented better. In general, borgmatic "officially" supports software that is actively supported by its maintainers, as this small volunteer effort has limited time. For instance, borgmatic just dropped support for Python 3.6, which was recently end-of-lifed. As a work-around, if you still want to use borgmatic, you could manually dump the database with a `before_backup` hook into a location specified in your `source_directories` so that the dump will be included in each backup. However, that wouldn't make use of any of borgmatic's built-in database dump or restore functionality. Thanks for your understanding.

witten added the

question / support

label 2022-02-09 05:12:56 +00:00

Firesphere commented 2022-02-09 05:16:13 +00:00

Author

Copy Link

Totally understandable. I sort-of expected this answer, but it never hurts to ask ;)

I wish I didn't have to deal with this old pile... but meh, such is life.

Totally understandable. I sort-of expected this answer, but it never hurts to ask ;) I wish I didn't have to deal with this old pile... but meh, such is life.

witten commented 2022-02-09 05:21:43 +00:00

Owner

Copy Link

Yup, I've been there. Good luck.. whatever you end up doing! And FWIW, the before_backup dump / after_backup remove dump method was the only way to use databases with borgmatic until not too long ago (~2 years ago).

Yup, I've been there. Good luck.. whatever you end up doing! And FWIW, the `before_backup` dump / `after_backup` remove dump method was the *only* way to use databases with borgmatic until not too long ago (~2 years ago).

witten closed this issue 2022-02-09 05:21:49 +00:00

Firesphere commented 2022-02-10 00:10:02 +00:00

Author

Copy Link

Yup, I've been there. Good luck.. whatever you end up doing! And FWIW, the before_backup dump / after_backup remove dump method was the only way to use databases with borgmatic until not too long ago (~2 years ago).

This is my life now :D

> Yup, I've been there. Good luck.. whatever you end up doing! And FWIW, the `before_backup` dump / `after_backup` remove dump method was the *only* way to use databases with borgmatic until not too long ago (~2 years ago). This is my life now :D

😆 1

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

spot-check

1.8.11

1.8.10

1.8.9

1.8.8

1.8.7

1.8.6

1.8.5

1.8.4

1.8.3

1.8.2

1.8.1

1.8.0

1.7.15

1.7.14

1.7.13

1.7.12

1.7.11

1.7.10

1.7.9

1.7.8

1.7.7

1.7.6

1.7.5

1.7.4

1.7.3

1.7.2

1.7.1

1.7.0

1.6.6

1.6.5

1.6.4

1.6.3

1.6.2

1.6.1

1.6.0

1.5.24

1.5.23

1.5.22

1.5.21

1.5.20

1.5.19

1.5.18

1.5.17

1.5.16

1.5.15

1.5.14

1.5.13

1.5.12

1.5.11

1.5.10

1.5.9

1.5.8

1.5.7

1.5.7.dev0

1.5.6

1.5.5

1.5.4

1.5.3

1.5.2

1.5.1

1.5.0

1.4.22

1.4.21

1.4.20

1.4.19

1.4.18

1.4.17

1.4.16

1.4.15

1.4.14

1.4.13

1.4.12

1.4.11

1.4.10

1.4.9

1.4.8

1.4.7

1.4.6

1.4.5

1.4.4

1.4.3

1.4.2

1.4.1

1.4.0

1.3.26

1.3.25

1.3.24

1.3.23

1.3.22

1.3.21

1.3.20

1.3.19

1.3.18

1.3.17

1.3.16

1.3.15

1.3.14

1.3.13

1.3.12

1.3.11

1.3.10

1.3.9

1.3.8

1.3.7

1.3.6

1.3.5

1.3.4

1.3.3

1.3.2

1.3.1

1.3.0

1.2.18

1.2.17

1.2.16

1.2.15

1.2.14

1.2.13

1.2.12

1.2.11

1.2.10

1.2.9

1.2.8

1.2.7

1.2.6

1.2.5

1.2.4

1.2.3

1.2.2

1.2.1

1.2.0

1.1.15

1.1.14

1.1.13

1.1.12

1.1.11

1.1.10

1.1.9

1.1.7

1.1.6

1.1.5

1.1.4

1.1.3

1.1.2

1.1.1

1.1.0

1.0.3

1.0.2

1.0.1

1.0.0

0.1.8

0.1.7

0.1.6

0.1.5

0.1.4

0.1.3

0.1.2

0.1.1

0.1.0

0.0.7

0.0.6

0.0.5

0.0.4

0.0.3

0.0.2

Labels

Clear labels   

bug

  

data loss

  

design finalized

  

good first issue

  

new feature area

  

question / support

  

security

  

waiting for response

No Label

bug

data loss

design finalized

good first issue

new feature area

question / support

security

waiting for response

Milestone

Clear milestone

No items

No Milestone

Assignees

Clear assignees

No Assignees

2 Participants

Notifications

Subscribe

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#497

No description provided.