From: Nico Sabbi <nicola.sabbi@poste.it>
To: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Configuration tips for very large database
Date: Sat, 14 Feb 2015 20:42:26 +0100
Message-ID: <54DFA522.4020407@poste.it> (raw)
In-Reply-To: <CAGTBQpb4_sk1hebZh3pekL=QxgMJCFOC-nxE_LW5_usSWrBjPQ@mail.gmail.com>
References: <54DD2872.3070603@poste.it>
<2034701464.2446674.1423780681188.JavaMail.yahoo@mail.yahoo.com>
<CAGTBQpb4_sk1hebZh3pekL=QxgMJCFOC-nxE_LW5_usSWrBjPQ@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
On 02/13/2015 12:19 AM, Claudio Freire wrote:
> I have a table with ~800M rows, wide ones, that runs reporting queries
> quite efficiently (usually seconds).
>
> Of course, the queries don't traverse the whole table. That wouldn't
> be efficient. That's probably the key there, don't make you database
> process the whole thing every time if you expect it to be scalable.
>
> What kind of queries are you running that have slowed down?
>
> Post an explain analyze so people can diagnose. Possibly it's a
> query/indexing issue rather than a hardware one.
>
Thanks everybody for the answers. At the moment I don't have the queries
at hand (saturday:-) ).
I'll post them next week.
I'd really like to avoid data partitioning if possible. It's a thing
that gives me a strong stomach ache.
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
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-performance@postgresql.org
Cc: nicola.sabbi@poste.it
Subject: Re: Configuration tips for very large database
In-Reply-To: <54DFA522.4020407@poste.it>
* 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