From: | Vincenzo Romano <vincenzo(dot)romano(at)notorand(dot)it> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Inheritance efficiency |
Date: | 2010-04-26 15:41:20 |
Message-ID: | u2y3eff28921004260841j90777a6co4267ad8ae4f36aa1@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2010/4/26 Bruce Momjian <bruce(at)momjian(dot)us>:
> Vincenzo Romano wrote:
>> Hi all.
>>
>> I'm wondering how efficient the inheritance can be.
>> I'm using the constraint exclusion feature and for each child table
>> (maybe but one) I have a proper CHECK constraint.
>> How efficient can the query planner be in choosing the right child
>> tables in the case of, say, thousands of them?
>> Would the selection process behave linearly, logarithmically or what?
>
> It is fine for dozens of child tables, but not thousands; it does need
> improvement.
This sounds like "linear" algorithms. Doesn't it?
>> And now it comes to my mind the same question for partial indexes.
>> That is, if I had a lot (really a lot) of small partial indexes over a
>> very large table, how efficient can the query planner be
>> in selecting the right indexes?
No info about this point (partial indexes)?
Is also this geared with linear algorithms ?
--
Vincenzo Romano
NotOrAnd Information Technologies
NON QVIETIS MARIBVS NAVTA PERITVS
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-04-26 15:43:28 | Re: Table Bloat still there after the Vacuum |
Previous Message | Cédric Villemain | 2010-04-26 15:38:42 | Re: Table Bloat still there after the Vacuum |