I think too that having the possibility of scheduling database maintenance
function right into the database would be a great feature. The first use case
that comes to my mind is this */5 cron job which runs psql just to clean out
old sessions and force a vacuum analyze.
On Wednesday 04 February 2009 19:42:27 Simon Riggs wrote:
> As A.M. says elsewhere, it would be good to have a trigger that fired a
> NOTIFY that was picked up by a scheduled job that LISTENs every 10
> minutes for certain events.
In another thread Hannu talked about a completely different need where
integrating a ticker (PGQ) would help. It seems this is just another need for
it, extended to the event producing and consuming facet of it.
- New fork to keep no more visible MVCC row version with timestamping
- Support for time travel facilities (SELECT ... AS OF 'yesterday'::date;)
- Timestamping done after the fact thanks to the ticker (timestamptz/txid)
> We need a place for code that is *not* directly initiated by a user's
> actions, yet works as part of a closed loop system.
In response to
pgsql-general by date
|Next:||From: David Wall||Date: 2009-02-05 18:10:12|
|Subject: Re: Array, bytea and large objects|
|Previous:||From: A.M.||Date: 2009-02-05 15:45:12|
|Subject: Re: Pet Peeves?|