From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: EXPIRE as a statement |
Date: | 2014-05-05 02:06:10 |
Message-ID: | 6779.1399255570@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> Blagoj Petrushev wrote
>> I know for example that redis has this feature, the EXPIRE / EXPIREAT
>> / TTL commands.
>> http://redis.io/commands/expire
One thought here is that recent versions of the SQL standard contain some
temporal-data features, which might well be usable for the purposes
envisioned here. I'd much rather see us implementing SQL-spec features
than randomly invented ones, so please take a look into the spec before
going too far with EXPIRE.
Having said that, I rather doubt that any such feature is likely to be
worth the implementation complexity and overhead. The previous suggestion
of a cron-like daemon is probably far more likely to be acceptable;
it'd be less work, have a lot more use-cases, and be less likely to add
overhead that's useless to users who don't need the feature.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David G Johnston | 2014-05-05 02:19:35 | Re: EXPIRE as a statement |
Previous Message | Haribabu Kommi | 2014-05-05 01:05:36 | Re: Per table autovacuum vacuum cost limit behaviour strange |