From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: WIP: getting rid of the pg_database flat file |
Date: | 2009-08-12 20:48:24 |
Message-ID: | 20090812204824.GS23840@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* Alvaro Herrera (alvherre(at)commandprompt(dot)com) wrote:
> No, that's for the workers. The launcher needs all the entries anyway.
> (I'm assuming it will be able to check visibility of tuples, correct?
> Hmm, it will need to run transactions in order to do that ...)
I realize I'm jumping into the middle of this with something unrelated.
My apologies. A feature I've wanted a couple of times and which I know
other people have asked for is being able to schedule tasks to run at
certain times. Similar to cron or scheduler, but in the database
instead of having to set up something outside.
I would expect it to use something similar to the autovacuum
launcher/worker system. I'm wondering if it would be possible to
consider how other autovacuum-like systems might be added in the future
when doing these changes.
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-08-12 21:22:11 | Re: Why is vacuum_freeze_min_age 100m? |
Previous Message | Zdenek Kotala | 2009-08-12 19:59:31 | Re: compilation with libeditpreferred is broken |