Re: Multithreaded query onto 4 postgresql instances

From: "mark" <dvlhntr(at)gmail(dot)com>
To: "'Alban Hertroys'" <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl>, "'Alessandro Candini'" <candini(at)meeo(dot)it>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: Multithreaded query onto 4 postgresql instances
Date: 2011-02-13 01:44:29
Message-ID: 000301cbcb1f$8f592580$ae0b7080$@com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> Otherwise you probably didn't gain anything
> by splitting your database up like that - you've just reduced the
> available resources on that single machine.
>

Unless that single machine has more resource than a single PG instance can
consume to satisfy one query. (see how much faster a greenplum single node
can be at some workloads on a server with lots of disk)

What is commonly considered commodity hardware often has plenty of spare
resources if deployed with stock PG in a data warehouse roll and doesn't
have many queries being run against it at any given time.

Of course if he doesn't have spare resources on the machine he might just be
making his life worse, and far more complex.

Just my thoughts, I don't consider myself an expert on the subject matter.
Mark

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message pasman pasmański 2011-02-13 07:09:31 Re: Heavy queries not run by user application
Previous Message Ruben Blanco 2011-02-13 01:11:52 Heavy queries not run by user application