Re: PostgreSQL Timeline

From: Mason S <masonlists(at)gmail(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Chris Travers <chris(dot)travers(at)gmail(dot)com>
Cc: damien clochard <damien(at)dalibo(dot)info>, PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org>
Subject: Re: PostgreSQL Timeline
Date: 2013-10-10 15:13:33
Message-ID: CA+rR5x0ojS3hKS=z03wvoQuQGoOoazXiYHd1cHdObJDZv5AauQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

On Thu, Oct 10, 2013 at 4:39 AM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com>wrote:

> On Thu, Oct 10, 2013 at 2:48 PM, Chris Travers <chris(dot)travers(at)gmail(dot)com>
> wrote:
> > Postgres-XC probably did more than anything else to kill a lot of the
> > clustering projects. Why use GridSQL when you can use Postgres-XC?
> Bookmarking this one :)
>

Because they are intended for different workloads. GridSQL handles ad hoc
analytical queries much better.

Try running DBT-1 (TPC-H) against GridSQL and Postgres-XC. You will get
nice scalability with GridSQL, but may be waiting for hours with
Postgres-XC... it sometimes ships everything to one single node for joining.

Postgres-XC does fine for OLTP workloads and analytical queries that do not
involve inter-node joins. GridSQL performs poorly for OLTP, but can handle
inter-node joins in parallel for analytical queries.

Use the right solution depending on your requirements.

That said, long term Postgres-XC could replace GridSQL if it improves in
this area. Postgres-XC could also replace pgpool-II today in some cases,
possibly more if we allow reads from data node slaves.

Regards,

Mason

In response to

Browse pgsql-advocacy by date

  From Date Subject
Next Message damien clochard 2013-10-10 21:18:13 Re: PostgreSQL Timeline
Previous Message Michael Paquier 2013-10-10 11:39:24 Re: PostgreSQL Timeline