pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
large table vs multiple smal tables
3+ messages / 3 participants
[nested] [flat]

* large table vs multiple smal tables
@ 2005-07-13 10:08  Nicolas Beaume <nicolas.beaume@univ-nantes.fr>
  0 siblings, 2 replies; 3+ messages in thread

From: Nicolas Beaume @ 2005-07-13 10:08 UTC (permalink / raw)
  To: pgsql-performance

Hello

I have a large database with 4 large tables (each containing at least 
200 000 rows, perhaps even 1 or 2 million) and i ask myself if it's 
better to split them into small tables (e.g tables of 2000 rows) to 
speed the access and the update of those tables (considering that i will 
have few update but a lot of reading).

Do you think it would be efficient ?

Nicolas, wondering if he hadn't be too greedy

-- 

-------------------------------------------------------------------------
« soyez ce que vous voudriez avoir l'air d'être » Lewis Caroll




^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: large table vs multiple smal tables
@ 2005-07-13 12:33  Kenneth Marshall <ktm@it.is.rice.edu>
  parent: Nicolas Beaume <nicolas.beaume@univ-nantes.fr>
  1 sibling, 0 replies; 3+ messages in thread

From: Kenneth Marshall @ 2005-07-13 12:33 UTC (permalink / raw)
  To: Nicolas Beaume <nicolas.beaume@univ-nantes.fr>; +Cc: pgsql-performance

Nicolas,

These sizes would not be considered large. I would leave them
as single tables.

Ken

On Wed, Jul 13, 2005 at 12:08:54PM +0200, Nicolas Beaume wrote:
> Hello
> 
> I have a large database with 4 large tables (each containing at least 
> 200 000 rows, perhaps even 1 or 2 million) and i ask myself if it's 
> better to split them into small tables (e.g tables of 2000 rows) to 
> speed the access and the update of those tables (considering that i will 
> have few update but a lot of reading).
> 
> Do you think it would be efficient ?
> 
> Nicolas, wondering if he hadn't be too greedy
> 
> -- 
> 
> -------------------------------------------------------------------------
> ? soyez ce que vous voudriez avoir l'air d'?tre ? Lewis Caroll
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: large table vs multiple smal tables
@ 2005-07-14 18:26  Jim C. Nasby <decibel@decibel.org>
  parent: Nicolas Beaume <nicolas.beaume@univ-nantes.fr>
  1 sibling, 0 replies; 3+ messages in thread

From: Jim C. Nasby @ 2005-07-14 18:26 UTC (permalink / raw)
  To: Nicolas Beaume <nicolas.beaume@univ-nantes.fr>; +Cc: pgsql-performance

On Wed, Jul 13, 2005 at 12:08:54PM +0200, Nicolas Beaume wrote:
> Hello
> 
> I have a large database with 4 large tables (each containing at least 
> 200 000 rows, perhaps even 1 or 2 million) and i ask myself if it's 
> better to split them into small tables (e.g tables of 2000 rows) to 
> speed the access and the update of those tables (considering that i will 
> have few update but a lot of reading).

2 million rows is nothing unless you're on a 486 or something. As for
your other question, remember the first rule of performance tuning:
don't tune unless you actually need to.
-- 
Jim C. Nasby, Database Consultant               decibel@decibel.org 
Give your computer some brain candy! www.distributed.net Team #1828

Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"



^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2005-07-14 18:26 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-07-13 10:08 large table vs multiple smal tables Nicolas Beaume <nicolas.beaume@univ-nantes.fr>
2005-07-13 12:33 ` Kenneth Marshall <ktm@it.is.rice.edu>
2005-07-14 18:26 ` Jim C. Nasby <decibel@decibel.org>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox