Skip site navigation (1) Skip section navigation (2)

Re: horizontal sharding

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: John R Pierce <pierce(at)hogranch(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: horizontal sharding
Date: 2009-06-15 18:49:39
Message-ID: dcc563d10906151149v6bc605cn6b13708b926063f5@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-general
On Mon, Jun 15, 2009 at 11:36 AM, John R Pierce<pierce(at)hogranch(dot)com> wrote:
> Jim Mlodgenski wrote:
>>
>>
>>    also is it possible to paritition without changing client code
>>
>> Yes, but it depends on the SQL in your client code. If you are just using
>> simple SQL with no stored functions, you should be able to slip in either
>> solution without changing the client code.
>
> what about queries that need to do joins or aggregate reporting across the
> partitions?!?  I can't see how that could be done transparently short of
> something like Oracle RAC.

If you use inheritance and therefore put the child tables on the same
server, it's invisible to the client that the table is partitioned.
Make sure you've got constraint_exclusion turned on.

In response to

pgsql-general by date

Next:From: Dann CorbitDate: 2009-06-15 18:51:09
Subject: Re: 10 TB database
Previous:From: Mike ToewsDate: 2009-06-15 18:23:27
Subject: Select ranges based on sequential breaks

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group