![]() I suspect if you take this route, you may find no problems. If that errors, we can be 99% sure that the problem is in the export from your unsupported database, and we can take it to Atlassian (technically, they don't have to help, you're unsupported, but they will try)Īfter that, upgrade your 8.5 to 8.13, and then postgres to 9.11 (Jira 8.13 supports 9.6 through to 11) The recommended way to do this would be to take the backup of the current system, reconnect it to an empty Postgres 9.6 database, and restore the backup into there. We wanted to test both PostgreSQL and MySQL on the same hardware, using the same tools and tests. What you should do is split this into two parts.įirst, take your 8.5.1 installation and move it from a broken database to a supported one. So instead, I found the chance to work with the Postgres Professional company and identify both the strong and weak points of the two databases an excellent opportunity. The complexities of those two don't add together, they multiply any problem, and make it pretty much impossible for us to tell you where the problem really is without asking you to do multiple runs with large amounts of expensive logging. Retool supports a wide range of databases, including MySQL, PostgreSQL. Your two processes are "change database" and "upgrade". Streamline your project workflow by automating the integration between Jira and. I'm curious to know why you put a known-broken (and unsupported) system in place, as that's one of the possible problems, but that's not really relevant. The preferred database is MySQL and Postgres. At the moment you're making two major structural changes at the same time, and it's impossible to know which one of them the actual problem is with. Generally, for best performance, most people prefer Linux-RedHat or CentOS as the first choice of distribution.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |