From: | david drummard <vijayspam(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: performance question related to pgsql |
Date: | 2006-02-10 21:26:07 |
Message-ID: | 9c89e2490602101326m60ce0930y9446cef99c45855e@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
hi stephen,
thanks very much for the response. Are there any special commands to analyze
the index before using the table. If i rename the table, will the indexes
still stay with the table ( i hope so).
best regards
vijay eranti
On 2/10/06, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
>
> * david drummard (vijayspam(at)gmail(dot)com) wrote:
> > My question is what is the best way to do step (1) so that after the
> copy is
> > done, the table is fully indexed and properly balanced and optimized
> for
> > query.
> > Should i create indexes before or after import ? I need to do this in
> > shortest period of time so that the data is always uptodate. Note that
> > incremental updates are not possible since almost every row will be
> changed
> > in the new file.
>
> Create indexes after import, definitely. analyze after indexes have
> been created. You don't need to vacuum if you're creating a whole new
> table each time. Remember that if you need to adjust analyze parameters
> for some reason that you'll need to do that on every table creation as
> well. Using COPY is a good approach. Not doing incremental updates
> when most of the rows are changing also makes sense.
>
> Thanks,
>
> Stephen
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (GNU/Linux)
>
> iD8DBQFD7Pu9rzgMPqB3kigRArthAJ4vgBzbUL/0YbeWu/luVFIGaP43rwCgkkf2
> 2Y7ADi6UEbhpl8CyDNC2jA8=
> =WhhZ
> -----END PGP SIGNATURE-----
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | C. Bensend | 2006-02-10 21:32:24 | Re: Is the database being VACUUMed? |
Previous Message | Brad Nicholson | 2006-02-10 21:19:37 | Re: Is the database being VACUUMed? |