Thread: Ask about large database?

On 18.01.2007 09:03, Thuy Nguyen wrote:
>   I am look for RDBMS solution for my web application, size of my database may be about 10GB-->500GB. How PostgreSQL
workwell or how must I config it?  
>   My application process data locally; one database has only one connection (not a server-client model).
>   Please tell me your suggestions!

PostgreSQL will work just fine in that situation, though it will really
show its power when you have a large amount of concurrent connections /
transactions.

You always need to configure PostgreSQL for a given workload.

See:

http://powerpostgresql.com/PerfList
http://powerpostgresql.com/Downloads/annotated_conf_80.html
http://powerpostgresql.com/PlanStats

and related documentation.


--
Regards,
Hannes Dorbath

On Thu, 2007-01-18 at 02:03, Thuy Nguyen wrote:
> Hi Sir/Madam!
> I am look for RDBMS solution for my web application, size of my
> database may be about 10GB-->500GB. How PostgreSQL work well or how
> must I config it?
> My application process data locally; one database has only one
> connection (not a server-client model).
> Please tell me your suggestions!

Not being flippant here, honest, but you haven't told us enough to
really know.  I've seen terabyte sized datasets that postgresql was very
fast on (relatively speaking) and gigabyte sized datasets that were a
horrible choice for.

Most of the time it's the processing methodology that determines if
pgsql is a good fit, not the size of the dataset.

Batch processing is generally not pgsql's strong suit.  It can do it,
and I've used it for it many a time, but often sed / awk / mysql / grep
/ php / perl are better tools for batch processing than pgsql.

So, tell us what you're gonna do.  Plus, it might be that with some
tweaks to your methods, pgsql can go from being a poor choice to being a
good one.