From: J. Andrew Rogers <jrogers@neopolitan.com>
To: Carlos Eduardo Smanioto <csmanioto@uol.com.br>
Cc: pgsql-performance@postgresql.org
Subject: Re: [OFF-TOPIC] - Known maximum size of the PostgreSQL
Date: 05 May 2004 14:11:29 -0700
Message-ID: <1083791489.11496.23.camel@localhost.localdomain> (raw)
In-Reply-To: <034d01c44b2e$ae9b2b00$cf00a8c0@smannote>
References: <034d01c44b2e$ae9b2b00$cf00a8c0@smannote>
On Sat, 2004-06-05 at 11:55, Carlos Eduardo Smanioto wrote:
> What's the case of bigger database PostgreSQL (so greate and amount of
> registers) that they know???
You might want to fix the month on your system time.
With respect to how big PostgreSQL databases can get in practice, these
are our two biggest implementations:
- 0.5 Tb GIS database (this maybe upwards of 600-700Gb now, I didn't
check)
- 10 Gb OLTP system with 70 million rows and a typical working set of
2-3 Gb.
Postgres is definitely capable of handling large pretty databases with
ease. There are some narrow types of workloads that it doesn't do so
well on, but for many normal DBMS loads it scales quite well.
j. andrew rogers
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: jrogers@neopolitan.com, csmanioto@uol.com.br
Subject: Re: [OFF-TOPIC] - Known maximum size of the PostgreSQL
In-Reply-To: <1083791489.11496.23.camel@localhost.localdomain>
* 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