Hi, On 2020-01-20 15:49:29 -0600, Justin Pryzby wrote: > On Mon, Jan 20, 2020 at 11:11:20AM -0800, Andres Freund wrote: > On Mon, Jan 20, 2020 at 11:11:20AM -0800, Andres Freund wrote: > > Alternatively we could push another context for each index inside > > lazy_vacuum_all_indexes(). There's been plenty bugs in indexes > > triggering problems, so that could be worthwhile. > > Did this too, although I'm not sure what kind of errors it'd find (?)
What do you mean with "kind of errors"? We had index corruptions that caused index vacuuming to fail, and there was no way to diagnose which table / index it was so far? > postgres=# SET client_min_messages=debug;SET statement_timeout=99; VACUUM > (VERBOSE, PARALLEL 0) t; > INFO: vacuuming "public.t" > DEBUG: "t_a_idx": vacuuming index > 2020-01-20 15:47:36.338 CST [20139] ERROR: canceling statement due to > statement timeout > 2020-01-20 15:47:36.338 CST [20139] CONTEXT: while vacuuming relation > "public.t_a_idx" > 2020-01-20 15:47:36.338 CST [20139] STATEMENT: VACUUM (VERBOSE, PARALLEL 0) > t; > ERROR: canceling statement due to statement timeout > CONTEXT: while vacuuming relation "public.t_a_idx" It'd be a bit nicer if it said index "public.t_a_idx" for relation "public.t". Greetings, Andres Freund
