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

Re: One large v. many small

From: "Josh Berkus" <josh(at)agliodbs(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Noah Silverman <noah(at)allresearch(dot)com>,pgsql-performance(at)postgresql(dot)org
Subject: Re: One large v. many small
Date: 2003-01-31 05:55:40
Message-ID: (view raw or whole thread)
Lists: pgsql-generalpgsql-performance

Well, there you have it:  a unanimous consensus of opinion.   You
should either combine all of your tables or not.  But definitely one or
the other.


Hope you feel informed now.


In response to


pgsql-performance by date

Next:From: Shridhar Daithankar<>Date: 2003-01-31 06:27:40
Subject: Re: One large v. many small
Previous:From: Curt SampsonDate: 2003-01-31 04:02:52
Subject: Re: Postgres 7.3.1 poor insert/update/search performance

pgsql-general by date

Next:From: Tom LaneDate: 2003-01-31 06:00:45
Subject: Re: 2D arrays in 7.3... actually, parser bug?
Previous:From: codeWarriorDate: 2003-01-31 05:37:33
Subject: Re: Perl DBI and placeheld values

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