On Wed, Jan 18, 2006 at 11:35:27AM +0100, Stephen Friedrich wrote: > Martijn van Oosterhout wrote: > >The problem AFAICS is that the planner is taking the results of two > >tables which are ordered by id and merging them. PostgreSQL doesn't > >have a Merge node type so it does this by concatentating the lists and > >sorting again. <snip> > Or wait, maybe postgres considers rows from the parent table, because > the parent table has no check constraint. Unfortunately according to the > doc I cannot define a check constraint on the parent table, because it > would be inherited by the other tables. Are you sure? I havn't tested it but the ALTER syntax allows you to say something like: ALTER TABLE ONLY foo ADD CONSTRAINT ... > There are problems with even simpler queries, e.g. > "select min(id) from call_sources where cdr_id = 10554;" is doing a > sequential scan. Even if it considers results from the parent table it > should > combine the results of two index scans. Same problem. Min/max want something sorted and the partitioning code doesn't do that yet. Have a nice day, -- Martijn van Oosterhout <kleptog@xxxxxxxxx> http://svana.org/kleptog/ > Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a > tool for doing 5% of the work and then sitting around waiting for someone > else to do the other 95% so you can sue them.
Attachment:
signature.asc
Description: Digital signature
