Hello all, Yesterday, a new release of the RPM definition has been released, in order to integrate many cool updates: https://git.postgresql.org/gitweb/?p=pgrpms.git;a=summary
And at 10PM yesterday, we encountered a problem on the postgresql instance upgrades that were performed pointing to the previous RPM definition. Using the latest tag is not in our team best practices. Is it possible to keep the last 2 versions? I made a quick search on the scripts contained into the GIT project: https://git.postgresql.org/gitweb/?p=pgrpms.git;a=summary, in order to see if it is possible, as it was defined in per-OS version until 2019 (search for pgdg-redhat-repo in https://download.postgresql.org/pub/repos/yum/9.5/redhat/rhel-7-x86_64/), but it looks difficult to handle (I got quickly lost in the multiple Makefiles). Thanks in advance for your help, Have a nice day, Thomas B Le jeu. 13 mai 2021 à 21:46, Dhanisha <dhanisha.phad...@schrodinger.com> a écrit : > Hi Devrim, > > Thank you for your response. > > I have tried your suggestion, but the error is still present. > > I get below stack trace when I run 'yum update' or 'yum install' > > > I have tried few more things > 1. If I specify --nogpgcheck in yum install or remove > pgdg-redhat-all.repo, > the error goes away. > 2. I have also specified their respective gpgkeys file. > > > > I don't think it's an issue with yum or the system at this point, as we can > reproduce it on other systems. > > Sincerely, > Dhanisha Phadate > > > > > -- > Sent from: > https://www.postgresql-archive.org/PostgreSQL-general-f1843780.html > > >
