From owner-freebsd-ports@FreeBSD.ORG Sat Jan 31 07:52:57 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D8D9016A4CE for ; Sat, 31 Jan 2004 07:52:57 -0800 (PST) Received: from bast.unixathome.org (bast.unixathome.org [66.11.174.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65AF643D53 for ; Sat, 31 Jan 2004 07:52:56 -0800 (PST) (envelope-from dan@langille.org) Received: from wocker (wocker.unixathome.org [192.168.0.99]) by bast.unixathome.org (Postfix) with ESMTP id 0786B3D28; Sat, 31 Jan 2004 10:52:53 -0500 (EST) From: "Dan Langille" To: Palle Girgensohn Date: Sat, 31 Jan 2004 10:52:53 -0500 MIME-Version: 1.0 Message-ID: <401B8905.6936.1A6A3212@localhost> Priority: normal In-reply-to: <18990000.1075563899@palle.girgensohn.se> References: <401B6403.8589.19D9A1B3@localhost> X-mailer: Pegasus Mail for Windows (v4.02a) Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: Quoted-printable Content-description: Mail message body cc: ports@freebsd.org Subject: Re: databases/postgresql7 dump + restore didn't include pgcrypto functions X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2004 15:52:58 -0000 On 31 Jan 2004 at 16:44, Palle Girgensohn wrote: > --On l=F6rdag, januari 31, 2004 08.14.59 -0500 Dan Langille > wrote: > > > On 31 Jan 2004 at 5:06, Palle Girgensohn wrote: > > > >> If I'm not wrong, this means that postgresql functions, at least thos= e > >> programmed in C and using elog, must be rebuilt when updating the ser= ver > >> 7.3 -> 7.4. > > > > Yes. This is confirmed by http://archives.postgresql.org/pgsql- > > general/2003-10/msg00667.php > > Cool. An echo in the Makefile would end up in the postgresql-contrib > makefile IMO, but would not have helped you, since you didn't use the po= rt. > If one does use the port, chances are pretty high that all pg ports will= be > updated together. I'm not sure an echo will do much good - too much > information makes ppl stop reading... The postgresql7 port is already > overloaded with echoes. This issue is not mentioned anywhere [that I could find] in the PostgreSQL HISTORY or INSTALL files. It is recorded many times in the archives, but that's not the place to put things such as this. The issue only arises is upgrading from PG < 7.4. Sorry, no more ideas here. -- Dan Langille : http://www.langille.org/ BSDCan - http://www.bsdcan.org/