| From: | Shridhar Daithankar <ghodechhap(at)ghodechhap(dot)net> |
|---|---|
| To: | Marco Colombo <pgsql(at)esiway(dot)net> |
| Cc: | Christopher Browne <cbbrowne(at)acm(dot)org>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Scheduler in Postgres |
| Date: | 2004-12-17 10:02:48 |
| Message-ID: | 200412171532.48513.ghodechhap@ghodechhap.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Friday 17 Dec 2004 3:20 pm, Marco Colombo wrote:
> Is the Oracle one _just_ that? A cron/at replacement? What about porting
> every UNIX utility to the DB engine (that would be a cross-platfrom Unix
> - wow)?
> Why don't they put web and application server functionality (apache and
> PHP) in the DB? No, wait... ehm... :-)
If one looks at the database and thinks, 'This is a storage engine with
programming abilities', then a in-DB scheduler isn't that much attractive
proposition.
Look at it and think 'This is an application server with flexbile data storage
engine for free' and it sounds lot more sensible.
It is all about perspective and it is not the same from one case to another.
I mean why would one write a PL/SQL application that counts to 1.3+ million
lines of code?..:-) But people do these sort of things..
Shridhar
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Riccardo G. Facchini | 2004-12-17 10:36:15 | Re: Scheduler in Postgres |
| Previous Message | Raymond O'Donnell | 2004-12-17 09:53:48 | Re: Cannot drop template1 |