I was running a long-running vacuum full, and then halfway thru that our
background vacuum process started.  As well as this, there was light
activity on a users table from which vacuum full was removing 90000 rows.

Then vacuum full failed after a while:

ERROR:  simple_heap_update: tuple concurrently updated


---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match

Reply via email to