Re: Performance issues of one vs. two split tables. - Mailing list pgsql-general

From Vivek Khera
Subject Re: Performance issues of one vs. two split tables.
Date
Msg-id 859D35EE-3502-40E5-901D-DEA8B71D6814@khera.org
Whole thread Raw
In response to Performance issues of one vs. two split tables.  (Bill Moseley <moseley@hank.org>)
List pgsql-general
On May 14, 2007, at 4:37 PM, Bill Moseley wrote:

> Say that there's also about 10 columns of settings or preferences for
> each user.  Are there any cases or reasons to have a separate
> "user_preferences" table vs. just placing all the columns together in
> one table?

when you have, say 65 million users, it makes sense to push the
ancillary info to another table to keep from having to copy too much
data when you update the main info (like last access time).

pgsql-general by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Postgres Printed Manuals
Next
From: Vivek Khera
Date:
Subject: Re: Performance issues of one vs. two split tables.