Re: Why does a simple query not use an obvious index? - Mailing list pgsql-performance

From Pierre-Frédéric Caillaud
Subject Re: Why does a simple query not use an obvious index?
Date
Msg-id opsdj8ke1rcq72hf@musicbox
Whole thread Raw
In response to Re: Why does a simple query not use an obvious index?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
    Another primary key trick :

    If you insert records with a serial primary key, and rarely delete them
or update the timestamp, you can use the primary key to compute an
approximate number of rows.

    a := SELECT pkey FROM table WHERE timestamp() > threshold ORDER BY
timestamp ASC LIMIT 1;
    b := SELECT pkey FROM table WHERE ORDER BY pkey DESC LIMIT 1;

    (b-a) is an approximate count.

    Performance is great because you only fetch two rows. Index scan is
guaranteed (LIMIT 1). On the downside, you get an approximation, and this
only works for tables where timestamp is a date of INSERT, timestamp
worrelated wiht pkey) not when timestamp is a date of UPDATE (uncorrelated
with pkey).

pgsql-performance by date:

Previous
From: Pierre-Frédéric Caillaud
Date:
Subject: Re: Why does a simple query not use an obvious index?
Next
From: Bruno Wolff III
Date:
Subject: Re: Why does a simple query not use an obvious index?