From: Jerry Sievers <gsievers19@comcast.net>
To: David G. Johnston <david.g.johnston@gmail.com>
Cc: Campbell\, Lance <lance@illinois.edu>
Cc: pgsql-admin\@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: pg_restore new parameter request
Date: Mon, 23 Nov 2015 11:37:45 -0600
Message-ID: <86fuzwaa6u.fsf@jerry.enova.com> (raw)
In-Reply-To: <CAKFQuwb4PxoWpdWv3BTTN0Q+P8wELuE3OGGZm9F0ZvAyDp_A8Q@mail.gmail.com>
References: <B75CD08C73BD3543B97E4EF3964B7D702015E9C6@CHIMBX1.ad.uillinois.edu>
<CAKFQuwb4PxoWpdWv3BTTN0Q+P8wELuE3OGGZm9F0ZvAyDp_A8Q@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
"David G. Johnston" <david.g.johnston@gmail.com> writes:
> On Mon, Nov 23, 2015 at 7:37 AM, Campbell, Lance <lance@illinois.edu> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: gsievers19@comcast.net, david.g.johnston@gmail.com, lance@illinois.edu
Subject: Re: pg_restore new parameter request
In-Reply-To: <86fuzwaa6u.fsf@jerry.enova.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox