I did think of including that optimization but I thought it was better (because conceptually easier) to show what I did show (the idea was to show the ease of use of the postgres interval datatype).
And remember that index-retrieval is not always faster. SeqScan is better than Index-retrieval when hitting a large part of the table (like when deleting 40 out of 100 rows (or keeping 60 days out of 'hundreds' of rows as the OP mentions)). Of course there is no way to know what the distribution in the OP's table is.
Indeed, for my example, it turns out seq scan is still preferred over index, with my original date data. Only if the number of deleted rows becomes small compared to the total rowcount, does Pg use the index. So yes, PostgreSQL /is/ extremely clever ;-)
The index-usable statement for postgres could be:
delete from t where d < now() - interval '2';
I tweaked my little program to accept an arg1=number of created rows and an arg2=number of rows to keep.
$ pm/1056374.sh 99 60 # create table with 99 rows, keep 60
DROP TABLE
SELECT 100
CREATE INDEX
ANALYZE
count | records_to_keep | records_to_dump
-------+-----------------+-----------------
100 | 60 | 40
(1 row)
QUERY PLAN
--------------------------------------------------------
Delete on t (cost=0.00..2.75 rows=39 width=6)
-> Seq Scan on t (cost=0.00..2.75 rows=39 width=6)
Filter: (d <= (now() - '60 days'::interval))
(3 rows)
DELETE 40
count | records_to_keep | records_to_dump
-------+-----------------+-----------------
60 | 60 | 0
(1 row)
$ pm/1056374.sh 999 990 # create table with 999 rows, keep 990
DROP TABLE
SELECT 1000
CREATE INDEX
ANALYZE
count | records_to_keep | records_to_dump
-------+-----------------+-----------------
1000 | 990 | 10
(1 row)
QUERY PLAN
----------------------------------------------------------------------
+-----
Delete on t (cost=0.28..8.45 rows=10 width=6)
-> Index Scan using d_date_idx on t (cost=0.28..8.45 rows=10 widt
+h=6)
Index Cond: (d <= (now() - '990 days'::interval))
(3 rows)
DELETE 10
count | records_to_keep | records_to_dump
-------+-----------------+-----------------
990 | 990 | 0
(1 row)
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.