hi florian
sorry for the late reply - it took almost a day to dump & reload the
data into 9.1b1.
how can i get postgres to use the indexes when querying the master
table?
I believe that this is a new feature in PostgreSQL 9.1 ("Allow
inheritance table queries to return meaningfully-sorted r
On 05/06/2011 05:13 PM, Thomas Hägi wrote:
the query "SELECT * FROM data.logs ORDER BY re_timestamp DESC LIMIT
100" does use seq scans on all tables instead of using the existing
indexes which takes ages. when issuing the the same query to one of
the child tables directly ("SELECT * FROM data.l
* Thomas Hägi:
> how can i get postgres to use the indexes when querying the master
> table?
I believe that this is a new feature in PostgreSQL 9.1 ("Allow
inheritance table queries to return meaningfully-sorted results").
--
Florian Weimer
BFK edv-consulting GmbH http://w
i have around 25mio records of data distributed yearly over 9 child
tables (data.logs_20xx) that inherit from the master table data.logs.
the tables are partitioned using the field "re_timestamp", which has
btree indexes defined on all tables.
the query "SELECT * FROM data.logs ORDER BY re_tim
