Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YLYQP-0003wb-I8 for pgsql-admin@arkaria.postgresql.org; Wed, 11 Feb 2015 14:37:57 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YLYQP-0005NN-26 for pgsql-admin@arkaria.postgresql.org; Wed, 11 Feb 2015 14:37:57 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YLYQO-0005ND-6e for pgsql-admin@postgresql.org; Wed, 11 Feb 2015 14:37:56 +0000 Received: from mail-yh0-x233.google.com ([2607:f8b0:4002:c01::233]) by magus.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1YLYQK-0000D6-P3 for pgsql-admin@postgresql.org; Wed, 11 Feb 2015 14:37:55 +0000 Received: by mail-yh0-f51.google.com with SMTP id b6so1487605yha.10 for ; Wed, 11 Feb 2015 06:37:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=ObUpCxO65kNObVk4e/RbuChHjes8HIb/ZT5COPAuD8s=; b=tT3GQPy7oT/9M5HJKXJXXyoxx7SCN3zpwCII/saaWNv8vnJxuVBuTBgtzoT9W3LZdp BkvKyjL8av+zJ/72d01Ko8Hgs8veX3PkQyZgnwzWKhQpbywC3Q9EHOHeMB75HYV1RpVf SVr36BvtU+EY5dmSMFA5fXZdYcHvJOJkHi5OW4YM8uaN+0+tv8iNSq39Vsfvv2o9mi52 uZty5AZOJgqyq20qjlswM3gsqQ2hcS/d7jmj1oYdBZYHkTc5mFXVPYaAoNsFynJ/irxw ODov0wFSv9M3/UFA840tg0ibFcD6H5zUzY7tvlIVZTFeDkg7aQ6uY46pY/0jw5ShluB6 /ToQ== X-Received: by 10.236.207.38 with SMTP id m26mr8793200yho.0.1423665470275; Wed, 11 Feb 2015 06:37:50 -0800 (PST) Received: from [192.168.254.3] (h77.89.102.166.static.ip.windstream.net. [166.102.89.77]) by mx.google.com with ESMTPSA id 62sm575712yhq.22.2015.02.11.06.37.49 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 Feb 2015 06:37:49 -0800 (PST) Message-ID: <54DB693A.7010705@gmail.com> Date: Wed, 11 Feb 2015 09:37:46 -0500 From: John Scalia User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: "David F. Skoll" , pgsql-admin@postgresql.org CC: Greg Clough Subject: Re: Streaming replication and WAL archiving References: <20150210172139.237ffb0b@ollie.roaringpenguin.com> <20150211092743.460e6bfe@hydrogen.roaringpenguin.com> In-Reply-To: <20150211092743.460e6bfe@hydrogen.roaringpenguin.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.7 (--) 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 I've had some issues with pg_upgrade and 9.4. For my test systems, as I didn't really have the resources to diagnose what was going on, I just used a pg_dumpall to unload the 9.3.3 instance and then just ran psql to load the output from pg_dumpall. The more wonderful part of installing different minor versions of postgresql, is that most O/S packages put the binaries and the default data directories in slightly different areas, so they can co-exist, just not necessarily run at the same time without specifying different connect ports. On 2/11/2015 9:27 AM, David F. Skoll wrote: > On Wed, 11 Feb 2015 09:04:44 +0000 > Greg Clough wrote: > >> Have you investigated the "Replication Slots" feature that's new in >> 9.4. It sounds like what you want: > Yes, it is exactly what I want... thanks! > > Now to plan the upgrade from 9.1 to 9.4... it's not exactly trivial. > The database is about 400GB which is large enough to be unwieldy and it > powers our anti-spam service... that means we can't be down for very > long. :( Time to re-familiarize myself with pg_upgrade... > > Regards, > > David. > > -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin