I wrote:
> "John Surcombe" writes:
>> When we 'EXPLAIN' this query, PostgreSQL says it is using the index
>> idx_receiveddatetime. The way the application is designed means that in
>> virtually all cases the query will have to scan a very long way into
>> idx_receiveddatetime to find the first re
>Don't insert data into an indexed table. A very important point with
>bulk-loading is that you should load all the data first, then create
>the indexes. Running multiple (different) CREATE INDEX queries in
>parallel can additionally save a lot of time. Also don't move data
>back and forth betwee
"John Surcombe" writes:
> When we 'EXPLAIN' this query, PostgreSQL says it is using the index
> idx_receiveddatetime. The way the application is designed means that in
> virtually all cases the query will have to scan a very long way into
> idx_receiveddatetime to find the first record where user
The row estimate is way off. Is autovacuum disabled?
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
Hello,
We are using PostgreSQL 9.0.3, compiled by Visual C++ build 1500,
32-bit, installed on Windows 2003 R2 32-bit.
We have an 'aisposition' table used for a GPS tracking application,
containing ~30 million rows and a number of indexes. Two of these are:
idx_receiveddatetime: indexes
