mirror of
https://github.com/eduardolat/pgbackweb.git
synced 2026-04-25 05:35:57 +03:00
[GH-ISSUE #43] add support for mysql and postgresql 9 - 10 #32
Labels
No labels
bug
confirmed next step
duplicate
enhancement
help wanted
in progress
in progress
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/pgbackweb#32
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @insinfo on GitHub (Sep 11, 2024).
Original GitHub issue: https://github.com/eduardolat/pgbackweb/issues/43
add support for mysql and postgresql 9 - 10
@eduardolat commented on GitHub (Sep 13, 2024):
Any version of PostgreSQL older than 12 is already "obsolete", you can see them at this link: https://www.postgresql.org/support/versioning/
Even version 12 has its EOL on November 14, 2024, and that is the main reason why it is not supported.
You should really consider upgrading your Postgres version, both for security and compatibility.
@insinfo commented on GitHub (Sep 14, 2024):
Where I work we have many legacy systems that we cannot update, the people who developed them are no longer with us and we have few resources and people, so it is not possible to simply update these applications, we have PostgreSQL 9.3, 10,11,12 and 16 databases and MySQL
@camaeel commented on GitHub (Sep 17, 2024):
@insinfo But don't expect maintainers of other software to keep those old versions. It may be very hard to have old library versions mixed with new ones in one software.
And this is also responsibility of management to keep enough people to maintain all the legacy apps that are in the company and also keep them up to date with current library versions and security vulnerabilities patched.
@eduardolat commented on GitHub (Sep 17, 2024):
@camaeel you are completly right. For the moment PG Back Web will only include the postgresql versions that are officially supported by them and in the future, older versions will be removed from the latest releases
https://www.postgresql.org/support/versioning/
@eduardolat commented on GitHub (Sep 17, 2024):
@insinfo In the company you work, they should update the software they depends on, or at least sponsor or help the project so we can add that kind of support
@insinfo commented on GitHub (Sep 19, 2024):
I work in a small city hall in a small town in the interior of Rio de Janeiro / Brazil, we simply do not have the financial resources and we also cannot find qualified workers with the salary we can offer. I believe that there are many who find themselves in this situation.
I understand that it is difficult to maintain support for older versions, but the PostgreSQL protocol has not changed much since version 9, and for simple databases that do not use specialized features of newer PostgreSQL versions there is no difference, and PostgreSQL 16 tools such as pg_dump and psql work with older databases without problems, and almost all PostgreSQL drivers work with older versions.
@insinfo commented on GitHub (Sep 19, 2024):
And this support for version 9-10 does not need to be forever, it could be limited to the current version and then deprecate them.
@insinfo commented on GitHub (Sep 19, 2024):
We can invariably update legacy applications, but this will be slow and will take time. I believe that in 3 or 4 years we will complete this task. Currently, we only have 2 developers to support several applications.