Re: Partitioning V schema

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Dave Potts <dave(dot)potts(at)pinan(dot)co(dot)uk>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Partitioning V schema
Date: 2013-09-20 16:47:08
Message-ID: CAMkU=1xLzeUty8cw8zka9Ubggcf+cJuqjPpRR-vjkJBnSbCA3Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Sep 19, 2013 at 12:02 AM, Dave Potts <dave(dot)potts(at)pinan(dot)co(dot)uk> wrote:

> Hi List
>
> I am looking for some general advice about the best was of splitting a
> large data table,I have 2 different choices, partitioning or different
> schemas.
>

I don't think there is much of a choice there. If you put them in
different schemas, then you are inherently partitioning the data. It just
a question of how you name your partitions, which is more of a naming issue
than a performance issue.

>
> The data table refers to the number of houses that can be include in a
> city, as such there are large number of records.
>
>
> I am wondering if decided to partition the table if the update
> speed/access might be faster that just declaring a different schema per
> city.
>

If you partition based on city, then there should be no meaningful
difference. If you partition based on something else, you would have to
describe what it is partitioned on, and what your access patterns are like.

Cheers,

Jeff

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Marc Mamin 2013-09-20 16:47:16 Re: PostgreSQL SQL Tricks: faster urldecode
Previous Message Merlin Moncure 2013-09-20 15:43:56 Re: PostgreSQL SQL Tricks: faster urldecode