Paul Robert, I'm curious about how things stand regarding the wiki you were going to write up about replication/failover/gluster. How have things gone for you since November with this?
I'm running spacewalk 1.7 on postgresql 8.4. I'm wanting to upgrade to postgresql 9.2 and spacewalk 1.9. I'd like to see about setting up some kind of replication / failover capability in the end. Do you (or anyone else for that matter) have any suggestions about what I should upgrade first? I see that there are at least 2 paths for upgrading postgresql since there's now the option of using the pg_upgrade tool to avoid the backup/reload method. Is there anyone who has successfully migrated the spacewalk DB using pg_upgrade who would be willing to talk about any issues related to that? And I see that the manual setup instructions on the wiki only provide instructions for pgsql 8.4. What version does the spacewalk-setup-embedded-postgresql package install? Does it give you a choice? How does it work? It would be nice to have a bit more elaboration on this in the wiki. Robert Boyd Sr System Engineer | Peoplefluent p. 919-645-2972 | c. 919-306-4681 e. [email protected] Visit: www.peoplefluent.com | Read: Peoplefluent Blog Follow: @peoplefluent | Download: iPad App -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Paul Robert Marino Sent: Tuesday, November 20, 2012 6:01 PM To: [email protected] Subject: Re: [Spacewalk-list] spacewalk-postgresql-1.8.6-1.el5.noarch.rpm requires postgresql84-contrib Ive been running on PostgreSQL 9.1 for some time and am about to switch to 9.2 for cascading streaming replication support which should work nicely with pgpool auto master failover and recovery. I'm using the RPMs from PGDG's repos here http://yum.postgresql.org/repopackages.php The only issue I ran into was this https://www.redhat.com/archives/spacewalk-list/2012-February/msg00052.html There is one more issue I found but its not a show stopper again its the JDBC driver unfortunately it breaks pgpools load balancing because it wraps all queries in a transaction even if the programer didn't ask it to. the result is all queries go to the master. This only prevents it from utilizing the backup node for speed but doesn't effect any critical functionality. I do intend to write a wiki doc soon on how to do this and utilize gluster to allow live live load balancing and failover between nodes. On Tue, Nov 20, 2012 at 2:12 PM, Jeremy Davis <[email protected]> wrote: > Hello Jan and All, > > Sorry I should have given a little background. I converted my > Spacewalk Oracle 11G(External DB) solution to Spacewalk PostgreSQL > 9.1(External DB) using Spacewalk 1.6 a while back. Now that 1.8 is > released I am cleaning things up a little bit as in order to get 1.6 > working with postgresql 9.1 I had to use the 84 packages and not 9.1 > on the app server. Now that I am cleaning up the packages I would like > to use the 9.1 packages as I feel it might clear some issues up that I > am seeing or maybe improve the situation a little. (Note: These issues > I am talking about seem to be fixed with bug fixes for 1.8 so I don't > think these are 9.1 specific issues just would like to rule out any > incompatibility issues by using the 9.1 packages with a 9.1 DB instead > of 8.4 packages.) > > Based on the Spacewalk wiki documentation it states the following > "please make sure the postgresql-contrib >= 8.4 (or postgresql84-contrib on > RHEL 5" > ) is installed on the PostgreSQL server." and "PostgreSQL 8.4+ as a > database backend." Which leads me to think that I could use a version > higher than 8.4. I also obtained a couple of fixes for escape issues > that I was having with 9.1. Seeing as how I was obtaining support for > 9.1 in the way of bugs being fixed I assumed it would be ok to use 9.1. > > What I am really asking is if we can update the rpm require lines to > reflect postgresql-contrib instead of postgresql84-contrib and use the > postgresql >= > 8.4 as the means to make sure we get at least 8.4 when installed via yum. > This also seems a lot cleaner than requiring postgresql84-contrib when > that package provides postgresql-contrib in the package. So it would > be really easy to change that to require just postgresql-contrib > instead of postgresql84-contrib. This would allow users to choose > which version of PostgreSQL to use, help smash any bugs that are found > with different versions, and allow Spacewalk to support newer version more > quickly. > > If I can't use 9.1 than I would recommend that you update the wiki or > allow me to update the wiki to change the documentation to state that > only 8.4 is a solid requirement and that you can't use a newer version. > > Thank you for your time and have a great day! > > Regards, > Jeremy > > On Tue, Nov 20, 2012 at 10:52 AM, Jan Pazdziora > <[email protected]> > wrote: >> >> On Tue, Nov 20, 2012 at 10:27:16AM -0700, Jeremy Davis wrote: >> > >> > I am trying to upgrade to Spacewalk 1.8 and hit a dependency issue >> > with spacewalk-postgresql package. It is requiring >> > postgresql84-contrib when I would like to use the >> > postgresql91-contrib. >> >> I really recommend separating the task of upgrading Spacewalk from >> the task of attempting to use different version of PostgreSQL than >> shipped with your version of RHEL/OS. With the later is introduce yet >> another layer of potential incompatibility to your setup. >> >> > Is there anyway that I can use >> > the 91 package instead of the 84 package? If I can't use the 9.1 >> > package would using the 84 packages with a 9.1 database going to >> > cause any issues? >> >> The contrib package has to match the PostgreSQL server version, >> really. Is the database server on the same machine as the Spacewalk >> installation, or is that an external database? _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
