Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: PG8.2.1 choosing slow seqscan over idx scan
- From: "Jeremy Haile" <jhaile(at)fastmail(dot)fm>
- To: "Scott Marlowe" <smarlowe(at)g2switchworks(dot)com>
- Cc: "Chad Wagner" <chad(dot)wagner(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-performance(at)postgresql(dot)org
- Subject: Re: PG8.2.1 choosing slow seqscan over idx scan
- Date: Wed, 17 Jan 2007 13:55:07 -0500
> Also, look at the thread going by about index bloat by 4x. You'll > likely want to reindex after a vacuum full since vacuum full doesn't > reclaim space in indexes and in fact often bloats indexes. Thanks for the pointer. That thread might indeed apply to my situation. I'm going to reindex the the table tonight. Jeremy Haile
- References:
- PG8.2.1 choosing slow seqscan over idx scan
- From: Jeremy Haile
- Re: PG8.2.1 choosing slow seqscan over idx scan
- From: Tom Lane
- Re: PG8.2.1 choosing slow seqscan over idx scan
- From: Jeremy Haile
- Re: PG8.2.1 choosing slow seqscan over idx scan
- From: Chad Wagner
- Re: PG8.2.1 choosing slow seqscan over idx scan
- From: Jeremy Haile
- Re: PG8.2.1 choosing slow seqscan over idx scan
- From: Scott Marlowe
- Re: PG8.2.1 choosing slow seqscan over idx scan
- From: Jeremy Haile
- Re: PG8.2.1 choosing slow seqscan over idx scan
- From: Scott Marlowe
- Re: PG8.2.1 choosing slow seqscan over idx scan
- From: Jeremy Haile
- Re: PG8.2.1 choosing slow seqscan over idx scan
- From: Scott Marlowe
- PG8.2.1 choosing slow seqscan over idx scan
- Prev by Date: Re: PG8.2.1 choosing slow seqscan over idx scan
- Next by Date: Re: PG8.2.1 choosing slow seqscan over idx scan
- Previous by thread: Re: PG8.2.1 choosing slow seqscan over idx scan
- Next by thread: Re: PG8.2.1 choosing slow seqscan over idx scan
- Indexes: