Dear Álvaro,
While testing REPACK CONCURRENTLY command with xid_wraparound module, noticed that
wraparound-autovac worker was terminated with an error like below.
``
ERROR: could not wait for concurrent REPACK
DETAIL: Process 41512 waits for REPACK running on process 41027
CONTEXT: waiting for ShareUpdateExclusiveLock on relation 16384 of database 5
automatic vacuum of table "postgres.public.test"
```
The behavior is different from other commands, like LOCK and maybe normal REPACK.
In these cases the autovac worker would wait till the command fails.
Is it an intentional behavior? If so, what is the advantage that we terminate the
failsafe vacuum?
Best regards,
Hayato Kuroda
FUJITSU LIMITED
