| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Wang Cheng <348448708(at)qq(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Proposal: Job Scheduler |
| Date: | 2024-06-06 10:53:38 |
| Message-ID: | 202406061053.nrg23pctc6wm@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2024-Jun-06, Dave Page wrote:
> It's this kind of choice that means it's unlikely we'd include any one
> option in PostgreSQL, much like various other tools such as failover
> managers or poolers.
TBH I see that more as a bug than as a feature, and I see the fact that
there are so many schedulers as a process failure. If we could have
_one_ scheduler in core that encompassed all the important features of
all the independent ones we have, with hooks or whatever to allow the
user to add any fringe features they need, that would probably lead to
less duplicative code and divergent UIs, and would be better for users
overall.
That's, of course, just my personal opinion.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Tachoires | 2024-06-06 10:58:12 | Compress ReorderBuffer spill files using LZ4 |
| Previous Message | Andrey M. Borodin | 2024-06-06 10:47:47 | Re: Injection points: preloading and runtime arguments |