Re: Smaller multiple tables or one large table?

From: Gabriele Bartolini <gabriele(dot)bartolini(at)2ndQuadrant(dot)it>
To: Benedict Holland <benedict(dot)m(dot)holland(at)gmail(dot)com>
Cc: John R Pierce <pierce(at)hogranch(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Smaller multiple tables or one large table?
Date: 2012-06-16 06:13:46
Message-ID: 4FDC241A.6040306@2ndQuadrant.it
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi Benedict,

Il 15/06/12 20:58, Benedict Holland ha scritto:
> The tables would have to be specified with a table pk constraint
> falling between two ranges. A view would then be created to manage all
> of the small tables with triggers handling insert and update
> operations. Select would have to be view specific but that is really
> cheap compared to updates. That should have the additional benefit of
> only hitting a specific table(s) with an update.
>
> Basically, I don't see how this particular configuration breaks and if
> PostgreSQL already has the ability to do this as it seems very useful
> to manage very large data sets.

What you are looking for is called 'partitioning' (horizontal
partitioning). I suggest that you read this chapter:
http://www.postgresql.org/docs/9.1/static/ddl-partitioning.html

Cheers,
Gabriele

--
Gabriele Bartolini - 2ndQuadrant Italia
PostgreSQL Training, Services and Support
gabriele(dot)bartolini(at)2ndQuadrant(dot)it | www.2ndQuadrant.it

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message hb@101-factory.eu 2012-06-16 15:04:42 any solution for doing a data file import spawning it on multiple processes
Previous Message Bruce Momjian 2012-06-16 00:01:51 Re: pg_upgrade: "pg_ctl failed to start the new server"