Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1a0v5i-0005To-NS for pgsql-admin@arkaria.postgresql.org; Mon, 23 Nov 2015 17:39:50 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1a0v5i-0001m6-9E for pgsql-admin@arkaria.postgresql.org; Mon, 23 Nov 2015 17:39:50 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1a0v45-0008Ir-4x for pgsql-admin@postgresql.org; Mon, 23 Nov 2015 17:38:09 +0000 Received: from resqmta-ch2-12v.sys.comcast.net ([2001:558:fe21:29:69:252:207:44]) by magus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1a0v41-0006uZ-7Y for pgsql-admin@postgresql.org; Mon, 23 Nov 2015 17:38:08 +0000 Received: from resomta-ch2-13v.sys.comcast.net ([69.252.207.109]) by resqmta-ch2-12v.sys.comcast.net with comcast id l5do1r0032N9P4d015dyFS; Mon, 23 Nov 2015 17:37:58 +0000 Received: from jerry.enova.com ([12.30.159.20]) by resomta-ch2-13v.sys.comcast.net with comcast id l5dm1r00C0ShjPw015dosd; Mon, 23 Nov 2015 17:37:56 +0000 Received: by jerry.enova.com (Postfix, from userid 1001) id 19D8D7401F0; Mon, 23 Nov 2015 11:37:46 -0600 (CST) From: Jerry Sievers To: "David G. Johnston" Cc: "Campbell\, Lance" , "pgsql-admin\@postgresql.org" Subject: Re: pg_restore new parameter request References: Date: Mon, 23 Nov 2015 11:37:45 -0600 In-Reply-To: (David G. Johnston's message of "Mon, 23 Nov 2015 07:55:06 -0700") Message-ID: <86fuzwaa6u.fsf@jerry.enova.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1448300278; bh=2VWeDOxkmYidhBo48avmCBlqPMeLmljWLLswmPm6Fzk=; h=Received:Received:Received:From:To:Subject:Date:Message-ID: MIME-Version:Content-Type; b=EvNpl07ZkLIqcAp9lCHBJOY1vHAeGOmj/rRFqus4e1M5dTp25DnYdVD/RGJx5CoUZ 7W0rSsa0BD/ZqFl0mxNqEZ9l28B+DdtzhaF4oVIGjSezq+vdvvswbS7MgQPDO5EZxV 77Y6na3an7fKzZEWhTp/PpWnTebNSmEqRZ/sZM6ltHlOE/bKuozlqwNzwV+SsjbjpA QsH8Trc3v+jsy+3N5h8Zb92z3vAL8gRS/g8u1WwJA47JcLKD4z10tYhIe74l68O31l Xio3k7VjnUFDeSidPnRaM+saA935nRODfr/VkX1CtQLTFg0PLNN2TKe9aIcas0mAPi bK609YHGR0Q9w== X-Pg-Spam-Score: -2.0 (--) 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 "David G. Johnston" writes: > On Mon, Nov 23, 2015 at 7:37 AM, Campbell, Lance wrote: > > Without the indexes the production system would run slower until they were applied but at least I would be up and running. > > ​At least until excessive sequential scanning overloads the I/O subsystem and you max out your processes, connections and/or timeouts... > > I'd be curious to know if you've ever tried dropping all of your indexes and running your systems under somewhat realistic load levels. Agreed. Unless the OPs app/DB are either tiny and utterly trivial or the app that they're in a hurry to get online again is something that just inserts data, then the notion of omitting all indexes is rather far-fetched and I bet not too generally useful. I can certainly imagine a scenario where there are very large tables which have some indexes created just to support reporting/analytics workloads which perhaps could be deferred in building till after most other application aspects are running. In such a case, then you'd want just to omit and/or reorder building those after everything else. FWIW > David J. > ​ >   > -- Jerry Sievers Postgres DBA/Development Consulting e: postgres.consulting@comcast.net p: 312.241.7800 -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin