| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Vick Khera <vivek(at)khera(dot)org> |
| Cc: | Postgres General Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Transaction table |
| Date: | 2010-03-21 20:29:30 |
| Message-ID: | dcc563d11003211329g2ddc3b96pd9d31f56e9013c49@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, Mar 21, 2010 at 1:30 PM, Vick Khera <vivek(at)khera(dot)org> wrote:
> Like the two Scott M's recommended, figure out your usage patterns and
> partition across those vectors to optimize those searches. I would
> not worry about optimizing the insert pattern.
Note that once the partitions get small enough, on bigger hardware,
there's often little need to index at that level anymore. If you're
pulling all the records from a 50 meg db file, it'll be read in well
under a second. Even if you hit a few partitions, it's still pretty
fast since it's at worst a sequential scan, or more likely a read from
OS level cache.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Szymon Guz | 2010-03-21 21:05:29 | strange |
| Previous Message | John Shott | 2010-03-21 20:20:53 | Re: Problems with "CREATE CAST" |