Q1. Why is EDB changing the repository structure?
A1. Our customers spoke. They told us the multi-part repository structure was too hard to work with. From setting up the repo configuration file, to selecting the right database server and tools repos, to getting the dependent packages installed. Then add the complication of operating in a disconnected network environment for some customers. It just needs to be easier.
Q2. When does this change go into effect?
A2. The new single repository structure for YUM goes into effect October 17 alongside the current structure to allow time for a transition for those customers who might have scripts tied to the current structure. The changes for the ZYPP (SLES) repository structure will be announced at a later time. There are no changes necessary for APT (Debian/Ubuntu).
Q3. What repositories will be changing with this announcement?
A3. What is changing are the EnterpriseDB YUM (RHEL/CentOS) repositories for the currently supported versions of the EDB Postgres Platform including 11, 10, 9.6, 9.5, and 9.4 on Intel and PowerPC architectures. For details on specific platforms currently supported see the EDB Supported Products and Platforms page on the website. After the change is in effect all new product releases will only be available in the new single repository structure; this includes the upcoming EDB Postgres Platform 12.
Q4. How are the EDB repositories changing?
A4. Effectively the new single repository structure simplifies the installation process by combining the current multi-part structure. For example, today in the YUM repository there is a repository per major database version, the tools, XDB, dependencies, and for the repo configuration file.
Q5. How do I upgrade?
A5. The first time you do an update after this change goes into effect, the repo rpm file will be updated with the new repository structure. Your current repo file is renamed as a snapshot/backup, and the values are copied into a new repo file. From this point forward updates will include the components from the single repository. For example, to upgrade to the new structure you effectively will run yum upgrade twice.
Q6. Do I have to upgrade?
A6. Yes. However, if you have a situation where your scripts rely on the existing structure, EDB will maintain both repository structures for 6 months to enable a transition period for our customers. After 6 months, the older structure will be available, but no longer synchronized with the newer structure. 12 months after the new single repository becomes available, the old structure will be removed.
Q7. I’m new to EDB Postgres, which repository structure should I use?
A7. For the best experience EDB recommends the newer, single repository structure. To use our repositories, you first have to install the edb-repo rpm which will point to the new single repository structure by default. If you have not setup your credentials for accessing the EDB repositories, start here: https://www.enterprisedb.com/repository-access-request.
Q8. My operating environment is not connected to the internet, how does this change impact me?
A8. The single repository structure also hosts a tarball of the repository files making it easier to download everything you need to install.
Q9. Where can I find more details?
A9. The installation guides for all products are updated to include information on using the new single repository structure. To find the installation guide for a specific product, please select from the product menu option at the top of the EDB documentation page https://www.enterprisedb.com/edb-docs/.