Re: vacuumdb --jobs deadlock: how to avoid pg_catalog ?

2020-05-14 Thread Eduard Rozenberg
rfect solution except for "well you can't actually use --jobs because you'll run into a deadlock and everybody knows that and nobody has a (good) solution for it" :). --Ed > On May 14, 2020, at 11:46, Adrian Klaver wrote: > > On 5/14/20 11:27 AM, Eduard Rozenberg

Re: vacuumdb --jobs deadlock: how to avoid pg_catalog ?

2020-05-14 Thread Eduard Rozenberg
e of is to list each table individually with "-t table1 -t table2..." to "vacuum db --jobs" which is not pleasant and not exceedingly beautiful. Thanks. > On May 14, 2020, at 10:35, Adrian Klaver wrote: > > On 5/14/20 8:35 AM, Eduard Rozenberg wrote: >> Hell

vacuumdb --jobs deadlock: how to avoid pg_catalog ?

2020-05-14 Thread Eduard Rozenberg
Hello there, I'm a long-time postgres user but vacuumdb newbie :). Using vacuumdb (v12.2) with '---jobs' to vacuum a v9.6 database on localhost with parallel processes: $ time vacuumdb --full --echo -U postgres --jobs=8 -d mydatabase_test -p 5434 --password As shown below I ran into t