Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id C4CBD2E3A57 for ; Wed, 19 Dec 2007 19:25:48 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 47357-02-2 for ; Wed, 19 Dec 2007 19:25:43 -0400 (AST) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.239]) by postgresql.org (Postfix) with ESMTP id 229FC2E31E4 for ; Wed, 19 Dec 2007 19:25:06 -0400 (AST) Received: by wr-out-0506.google.com with SMTP id 58so2593343wri.10 for ; Wed, 19 Dec 2007 15:25:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=uAKP/W7oAaLILbuTDFBVHjFUYMWQn0VKbVbzSqYutHI=; b=D6TXJlIwT579wGOFh4gt13gBL0kYVGNdx6brVJQ1bT0zPxOOcXyETaLyWyzZmI9OWxASru0GZJJzZnoTmpb27y4ctDCJ8bqRa9nQOLGk/Ql9K2IVPnPGKkgORxlnNJDv4zraf3qqoTwnq0uEgYJCGwY18dnk2KZTPO1jgt2sHtw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=FRJNlc6iSr1+i9Hb4LvOyli04Ceont3GSX/Mih5x62iXnGbXVM8O4V7T/vKjSR7qtAZnpublWodz2wd4ndlguq3ymyN6z2pegaqSd34MWd17qH7JKQArmfDK5VWO+VkLGQeOsJVBs2uip5rquurvW27KnTChk/HYUza1Y2RbaSI= Received: by 10.143.6.1 with SMTP id j1mr3626479wfi.45.1198106703264; Wed, 19 Dec 2007 15:25:03 -0800 (PST) Received: by 10.142.143.6 with HTTP; Wed, 19 Dec 2007 15:25:03 -0800 (PST) Message-ID: Date: Wed, 19 Dec 2007 17:25:03 -0600 From: "Scott Marlowe" To: "olivier.boissard@cerene.fr" Subject: Re: How to uses self query plan Cc: "Guillaume Lelarge" , pgsql-admin@postgresql.org In-Reply-To: <4769A698.9070700@cerene.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <476847DB.9090401@cerene.fr> <4768CEEF.9060506@cerene.fr> <476999FC.9090306@cerene.fr> <47699CBB.7080607@lelarge.info> <4769A698.9070700@cerene.fr> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200712/185 X-Sequence-Number: 27702 On Dec 19, 2007 5:17 PM, olivier.boissard@cerene.fr wrote: > Guillaume Lelarge a =E9crit : > > olivier.boissard@cerene.fr wrote: > > > >> You're right . > >> I will begin by migrate postgresql version. > >> postgresql is now to 8.3 version . A lot of performance inprovements > >> have been made in this last version . > >> In any case I must do a pg_dump/pg_restore. > >> So , Should I try directly 8.3 version or is it more cautious to stay = in > >> 8.1.x version ? > >> > >> > > > > It mostly depends on you. PostgreSQL 8.3 is still in beta phase. So, if > > you're also on development stage, you can use 8.3. Otherwise, it's > > better to use the latest stable available, which means 8.2.5. > > > > > > > I want in fact to make test on a server before , when validated migrate > on production server , so 8.2.5 is more appropriate. > Will I be able to keep my postgresql.conf file or is it not compatible ? No, you'll need to edit the new one by hand to reflect the changes you've made in the old one. Some things get renamed from one to the next, and often newer versions of pgsql have new settings you that the old version's postgresql.conf wouldn't know about.