| From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
|---|---|
| To: | Þórhallur Hálfdánarson <tolli(at)tol(dot)li> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Scheduled jobs |
| Date: | 2003-05-13 21:51:28 |
| Message-ID: | Pine.LNX.4.33.0305131548130.29172-100000@css120.ihs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
OK, here's an idea. You write a set of stored procs that let you do
something like:
insert into batch_jobs ('..... I'm not sure what we'd put here...)
then, postgresql has a crontab entry that uses something like redhats
runparts script to run the SQL commands it finds in the table.
I.e. the jobs could be scheduled by something as simple as a query, and
removed as well. Just need a postgresql cron that runs every 5 minutes or
whatever resolution you need.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2003-05-13 21:55:41 | Re: How are null's stored? -- Some numbers |
| Previous Message | Þórhallur Hálfdánarson | 2003-05-13 21:09:16 | Re: Scheduled jobs |