Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Y9D2p-00024M-Tm for pgsql-admin@arkaria.postgresql.org; Thu, 08 Jan 2015 13:22:36 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Y9D2o-0004Gw-UT for pgsql-admin@arkaria.postgresql.org; Thu, 08 Jan 2015 13:22:34 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1Y9ACO-0004Ki-Vz for pgsql-admin@postgresql.org; Thu, 08 Jan 2015 10:20:17 +0000 Received: from kwest.co ([83.217.171.43]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Y9ACH-00043T-Nm for pgsql-admin@postgresql.org; Thu, 08 Jan 2015 10:20:15 +0000 Message-ID: <54AE59CE.5010309@kwest.co> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kwest.co; s=default; t=1420712407; bh=nbo5NltFyGuBLJNXsD8UOFXk5cFLefmFRS5d25wnIpQ=; h=Date:From:To:Subject; b=vE2P75/ce0EfxFXZ2jK7eyBHFspgVxJRBgiziTCcKZrTlZ+T7QbF9yzcXFiVEn2h7 EGTr/HKEkimk+zcWMUyCEKh4/djIV7tQ8GTVaBdkHAUy5dI9vSJLF15E4lMEsNJDNy FTEjV3lZdBxMnAoGJlnf6Qkip1TMQd4zmyo1NRdc= Date: Thu, 08 Jan 2015 10:19:58 +0000 From: Kieran User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:34.0) Gecko/20100101 Thunderbird/34.0 MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: First point release of 9.4 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -0.1 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org Hi We are looking to upgrade from 9.3 to 9.4 but our first attempt resulted in the index row size 1440 exceeds maximum 1352 for index GIN index problem. Is the best option to wait for a point release to fix this? My second question is rather obvious, sorry. Have you thought about when this would be? I guess the comments on the fix were right when it said it could bite a lot of upgraders. Many Thanks Kieran -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin