Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 6DE6B633E6E for ; Fri, 6 Mar 2009 18:07:30 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 68136-08 for ; Fri, 6 Mar 2009 18:07:28 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from regoc.srce.hr (regoc.srce.hr [161.53.2.69]) by mail.postgresql.org (Postfix) with ESMTP id C3E476330DA for ; Fri, 6 Mar 2009 18:07:28 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by regoc.srce.hr (Postfix) with ESMTP id E71431072AE for ; Fri, 6 Mar 2009 23:07:26 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at smtp.srce.hr Received: from regoc.srce.hr ([127.0.0.1]) by localhost (regoc.srce.hr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FUx7KuHTFHqx for ; Fri, 6 Mar 2009 23:07:26 +0100 (CET) Received: from alphacentauri (93-141-86-87.adsl.net.t-com.hr [93.141.86.87]) by regoc.srce.hr (Postfix) with ESMTPSA id 08088107276 for ; Fri, 6 Mar 2009 23:07:25 +0100 (CET) Date: Fri, 6 Mar 2009 23:07:24 +0100 From: Jakov Sosic To: pgsql-admin@postgresql.org Subject: Re: using pgdg repo Message-ID: <20090306230724.759f9709@alphacentauri> In-Reply-To: References: <20090306222102.42dfc206@alphacentauri> Organization: SRCE X-Mailer: Claws Mail 3.7.0 (GTK+ 2.12.11; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200903/97 X-Sequence-Number: 31597 On Fri, 6 Mar 2009 15:59:08 -0600 (CST) Richard Ray wrote: Maybe priorities are broken? Maybe some other repo than pgdg3 has higher priority for postgresql, and yum then won't upgrade postgresql because it already has newer version than for example base/updates? try leaving only pgdg83.repo in /etc/yum.repos.d/ and moving all others somewhere temporary, and then add back one repo at a time, and you'll notice when stuff breaks. I have one cluster which wants to upgrade from 8.3.4 to 8.3.6, but I am not allowed to do it because of possible downtime/problems... And it bugs me almost a few months now, so I don't know what your problem can be, but the repos seem fine :( -- | Jakov Sosic | ICQ: 28410271 | PGP: 0x965CAE2D | ================================================================= | start fighting cancer -> http://www.worldcommunitygrid.org/ |