From: Pablo Alcaraz <pabloa@laotraesquina.com.ar>
To: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: TB-sized databases
Date: Tue, 27 Nov 2007 18:06:34 -0500
Message-ID: <474CA2FA.2020201@laotraesquina.com.ar> (raw)
In-Reply-To: <1196197045.4246.1154.camel@ebony.site>
References: <4544e0330711260904g45d893a8ub1731e245aa8fc84@mail.gmail.com>
<474B1407.3090607@laotraesquina.com.ar>
<474B1B8C.1030505@gmail.com>
<4544e0330711271218h56ce4cc3p280a9fefff24583d@mail.gmail.com>
<1196197045.4246.1154.camel@ebony.site>
Simon Riggs wrote:
> All of those responses have cooked up quite a few topics into one. Large
> databases might mean text warehouses, XML message stores, relational
> archives and fact-based business data warehouses.
>
> The main thing is that TB-sized databases are performance critical. So
> it all depends upon your workload really as to how well PostgreSQL, or
> another other RDBMS vendor can handle them.
>
>
> Anyway, my reason for replying to this thread is that I'm planning
> changes for PostgreSQL 8.4+ that will make allow us to get bigger and
> faster databases. If anybody has specific concerns then I'd like to hear
> them so I can consider those things in the planning stages
it would be nice to do something with selects so we can recover a rowset
on huge tables using a criteria with indexes without fall running a full
scan.
In my opinion, by definition, a huge database sooner or later will have
tables far bigger than RAM available (same for their indexes). I think
the queries need to be solved using indexes enough smart to be fast on disk.
Pablo
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: pabloa@laotraesquina.com.ar
Subject: Re: TB-sized databases
In-Reply-To: <474CA2FA.2020201@laotraesquina.com.ar>
* 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