| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | Nick Fankhauser <nickf(at)ontko(dot)com> |
| Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Optimizing a condition based on an a very unequally |
| Date: | 2002-03-13 21:21:38 |
| Message-ID: | 20020313131759.B86474-100000@megazone23.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Wed, 13 Mar 2002, Nick Fankhauser wrote:
> Thanks for the answer! ...but now I have more questions:
>
> Is it true that if I use this condition in a join that further constrains
> the results, this might use the index?
If there were other conditions, it may do so.
> Does PGSQL know that few or many rows will be returned because of data
> gathered from the last vacuum?
I'd guess the last analyze (or vacuum analyze).
> What do you mean by "tuple validity?" can't this query be resolved entirely
> based on the index?
Not currently, because the index doesn't know if the row can be seen by
your transaction. There may be rows that are valid for some transactions
but not yours that also have index entries.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James Kelty | 2002-03-13 21:41:27 | Order by clause in 'select distinct'? |
| Previous Message | bangh | 2002-03-13 20:40:05 | Re: Update 6.5 database files to 7.0 |