Thanks to Dejan Lekic (Deyan) on #ingres for inspiring me to write this short “how to” on building the community edition of Ingres 9.2 on 64-bit openSUSE 11.1. Currently (2009-07-24) there is no 64-bit Linux binaries of the community edition of Ingres 9.2 available at the Ingres ESD site. Because of this, the only way to run the community edition of 64-bit Ingres version 9.2 on Linux is to build it by yourself. In this posting I shortly describe the steps to get it built on 64-bit openSUSE 11.1.
I like to keep Ingres installations up to date by upgrading them occasionally by using the latest patches from ESD. Since I am a responsible DBA, I always read through the list of fixed bugs (“Bugs addressed with this patch” section in the readme file). Some bug fixes even need special attention (marked with “ATTENTION”), so it would be careless not to read the readme file, which is included with the patch.
Ingres patches are cumulative, meaning that each patch also contain the fixes included in the previous patches. Since the list of fixed bugs is ordered by bug numbers and not chronologically, it’s pretty hard to figure what have been fixed since previous installed patch. For example there’s 145 new bug fixes between patches 13322 and 13435.
Here’s a simple tip, how to compare two readme files on Linux using command line tools. First, save the readme files on disk with names p13322.html and p13435.html. Then run
grep "Bug " p13322.html | perl -p -e 's/<.*?>//g' > p13322.txt
grep "Bug " p13435.html | perl -p -e 's/<.*?>//g' > p13435.txt
Now you have a simple listing of bugs fixed in the patches. You can then use diff to compare, what have been fixed between 13322 and 13435:
diff -u p13322.txt p13435.txt | grep "^+" | less
The best thing would be, if Ingres Co. provided their customers a simple web application, which could be used to check these. Until that… use this tip or propose a better one!