I've installed the development packages mentioned below - and they went in just fine. They fixed the bug that I'd run into, and are working just fine on a pretty busy dual proc opteron database server. Dunno what standard you want to hold packages to before development packages are considered "release ready" - but it looks pretty good to me so far. Pakcages installed, both on X86/64 and X86/32: [root at kepler ~]# rpm -qa | grep postgre postgresql-server-8.1.2-1.c4 postgresql-test-8.1.2-1.c4 compat-postgresql-libs-3_x86_64-4.c4.centos postgresql-8.1.2-1.c4 postgresql-contrib-8.1.2-1.c4 postgresql-docs-8.1.2-1.c4 postgresql-libs-8.1.2-1.c4 postgresql-devel-8.1.2-1.c4 -Ben On Wednesday 25 January 2006 13:57, Jim Perrin wrote: > > I got the debuginfo package, installed, and found that the problem comes down > > to a bug fixed in PG 8.1.1, and the current release seems to be 8.1.2 - any > > chance this can be updated? > > These aren't RHEL production packages that are rebuilt. These packages > are from fedora and are still on our development list. Please keep > this in mind when using them. I'm running them through the build > system now, so they should be up in a couple hours. > > > > This is a production server, so I REALLY don't want to leave the CentOS build > > environment... > > These are still in our DEVELOPMENT repository because they haven't had > enough feedback to make it to centosplus yet. Please keep this in mind > and test them appropriately in your environment before rolling them > into production. > > > -- > Jim Perrin > System Architect - UIT > Ft Gordon & US Army Signal Center > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > -- "The best way to predict the future is to invent it." - XEROX PARC slogan, circa 1978