Re: Operational performance: one big table versus many smaller tables

From: Richard Huxton <dev(at)archonet(dot)com>
To: David Wall <d(dot)wall(at)computer(dot)org>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Operational performance: one big table versus many smaller tables
Date: 2009-10-27 09:12:00
Message-ID: 4AE6B960.801@archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

David Wall wrote:
> If I have various record types that are "one up" records that are
> structurally similar (same columns) and are mostly retrieved one at a
> time by its primary key, is there any performance or operational benefit
> to having millions of such records split across multiple tables (say by
> their application-level purpose) rather than all in one big table?

Probably doesn't matter if you're accessing by pkey (and hence index).
Certainly not when you're talking about a few million rows. Arrange your
tables so they have meaning and only change that if necessary.

--
Richard Huxton
Archonet Ltd

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Richard Huxton 2009-10-27 09:17:59 Re: design, ref integrity and performance
Previous Message Ivan Sergio Borgonovo 2009-10-27 09:05:18 design, ref integrity and performance