From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24317 invoked by alias); 1 Nov 2004 16:36:40 -0000 Mailing-List: contact rhdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: rhdb-owner@sources.redhat.com Received: (qmail 24310 invoked from network); 1 Nov 2004 16:36:39 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 1 Nov 2004 16:36:39 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id iA1Gadte020940 for ; Mon, 1 Nov 2004 11:36:39 -0500 Received: from sss.pgh.pa.us (sebastian-int.corp.redhat.com [172.16.52.221]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id iA1GaTr00851; Mon, 1 Nov 2004 11:36:29 -0500 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id iA1GaRnB014574; Mon, 1 Nov 2004 11:36:27 -0500 (EST) From: Tom Lane To: John Allgood cc: rhdb@sources.redhat.com Subject: Re: Problems with RHDB 3.0 In-reply-to: <41862A46.6030400@turbocorp.com> References: <41862A46.6030400@turbocorp.com> Comments: In-reply-to John Allgood message dated "Mon, 01 Nov 2004 07:21:26 -0500" Date: Mon, 01 Nov 2004 16:36:00 -0000 Message-ID: <14573.1099326986@sss.pgh.pa.us> X-SW-Source: 2004-q4/txt/msg00002.txt.bz2 John Allgood writes: > We have discovered a problem with plpgsql on Redhat Database 3.0 The > problem is fixed with Postgres 7.4. Is there is a new version of Redhat > Database on the horizon and what can we expect for the new version. "7.4 > or 8.0.". We are trying to get an idea on what direction we need to go in. Well, the road map looks like this: RHEL3 will use rh-postgresql 7.3.* until end of life; an upgrade to a new major Postgres version is out of the question because of our backward-compatibility requirements for that product. Fedora Core 3 (to become RHEL4) currently uses Postgres 7.4.*, and I am surely hoping that PG 8.0 is out in time that it can be the long-term- supported version for RHEL4. Note that we have dropped the "RHDB" branding in this version and gone back to calling it plain PostgreSQL. As far as your immediate problem goes, depending on what the issue is, it might or might not be feasible to back-port a fix into rh-postgresql 7.3. You didn't give any details... regards, tom lane Red Hat Database project