Re: Optimizer oddness, possibly compounded in 8.1 - Mailing list pgsql-hackers

From Hannu Krosing
Subject Re: Optimizer oddness, possibly compounded in 8.1
Date
Msg-id 1133878335.3608.3.camel@localhost.localdomain
Whole thread Raw
In response to Re: Optimizer oddness, possibly compounded in 8.1  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: Optimizer oddness, possibly compounded in 8.1  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
Ühel kenal päeval, L, 2005-12-03 kell 09:21, kirjutas Simon Riggs:

> First off, I think we need to do some more work on partitioning so that
> some knowledge about the union set is understood by the optimizer. At
> the moment there is no concept of partition key, so its hard to spot
> when two union sets have the same key to allow pushdown.

One of the easier cases would be non-overlapping (exclusive) constraints
on union subtables on the joined column.

This could serve as a "partition key", or in case of many nonoverlapping
columns (ex.: table is partitioned by date and region), as many
partition keys.

-------------
Hannu




pgsql-hackers by date:

Previous
From: Markus Schiltknecht
Date:
Subject: Re: Replication on the backend
Next
From: Tom Lane
Date:
Subject: Re: [PATCHES] snprintf() argument reordering not working