| From: | "Gilberto Castillo" <gilberto(dot)castillo(at)etecsa(dot)cu> |
|---|---|
| To: | "Dimitri Fontaine" <dimitri(at)2ndQuadrant(dot)fr> |
| Cc: | "Atri Sharma" <atri(dot)jiit(at)gmail(dot)com>, "Thom Brown" <thom(at)linux(dot)com>, "Josh Berkus" <josh(at)agliodbs(dot)com>, "PostgreSQL Advocacy" <pgsql-advocacy(at)postgresql(dot)org>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Call for Google Summer of Code mentors, admins |
| Date: | 2013-03-21 12:14:02 |
| Message-ID: | 40847.192.168.207.54.1363868042.squirrel@webmail.etecsa.cu |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers |
>
> Atri Sharma <atri(dot)jiit(at)gmail(dot)com> writes:
>> We can use a scheduling algorithm, and can define a pool of tasks as
>> well as
>> a time constraint for the amount of time which can be used for running
>> the
>> tasks.Then, a scheduling algorithm can pick tasks from the pool based on
>> priorities and the time duration of a task.I can see a dynamic
>> programming
>> solution to this problem.
>
> I think mcron already implements it all and is made to be embedded into
> a larger program.
>
> http://www.gnu.org/software/mcron/
I wonder if we can add the domain, something like:
SELECT * FROM DOMAINS mydom;
Returns
{"a", "b", "c", "d"}
Their content.
Saludos,
Gilberto Castillo
La Habana, Cuba
| Attachment | Content-Type | Size |
|---|---|---|
| unknown_filename | text/plain | 179 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Basil Bourque | 2013-03-22 09:03:49 | Re: Call for Google Summer of Code mentors, admins |
| Previous Message | Thom Brown | 2013-03-21 08:53:15 | Re: [pgsql-advocacy] Call for Google Summer of Code mentors, admins |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Euler Taveira | 2013-03-21 14:43:51 | Re: SIGHUP not received by custom bgworkers if postmaster is notified |
| Previous Message | Heikki Linnakangas | 2013-03-21 09:23:28 | pgsql: Fix "element <@ range" cost estimation. |