Re: [HACKERS] pg_terminate_backend can terminate background workersand autovacuum launchers
От | Alvaro Herrera |
---|---|
Тема | Re: [HACKERS] pg_terminate_backend can terminate background workersand autovacuum launchers |
Дата | |
Msg-id | 20170623200701.erac2hona6rwbbz7@alvherre.pgsql обсуждение исходный текст |
Ответ на | Re: [HACKERS] pg_terminate_backend can terminate background workersand autovacuum launchers (Yugo Nagata <nagata@sraoss.co.jp>) |
Ответы |
Re: [HACKERS] pg_terminate_backend can terminate background workersand autovacuum launchers
Re: [HACKERS] pg_terminate_backend can terminate background workersand autovacuum launchers |
Список | pgsql-hackers |
Yugo Nagata wrote: > I tried to make it. Patch attached. > > It is easy and simple. Although I haven't tried for autovacuum worker, > I confirmed I can change other process' parameters without affecting others. > Do you want this in PG? One advantage of this gadget is that you can signal backends that you own without being superuser, so +1 for the general idea. (Please do create a fresh thread so that this can be appropriately linked to in commitfest app, though.) You need a much bigger patch for the autovacuum worker. The use case I had in mind is that you have a maintenance window and can run fast vacuuming during it, but if the table is large and vacuum can't finish within that window then you want vacuum to slow down, without stopping it completely. But implementing this requires juggling the stdVacuumCostDelay/Limit values during the reload, which are currently read at start of vacuuming only; the working values are overwritten from those during a rebalance. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: