On Thu, 15 Feb 2018 17:40:48 +0100 Meikel Bisping <info@xxxxxxxxxxx> wrote: > Hello, > > we have lots of scripts which issue individual vacuum commands to tables > like "vacuum full gxstage_bs" but also general "vaccum full" commands. > Until now these scripts run sequentially and there are no problems. > Now the idea is to run some scripts in parallel, my question is if > parallel vacuum commands can lead to a lock in 10.2? > Unfortunately it isn't easy to change the scripts and rely on > auto-vacuum since they are installed on lots of customers' hosts and > installing updates is very complex. They lock already. Running in parallel isn't going to lead to any new locks. I don't think that's what you're asking, though. I'm guessing that what you're asking is are you going to experience deadlocks or other types of unresolvable lock scenarios. By design, no. In my experience, no. In the real world ... it's always possible that you will uncover some edge-case bug that leads to an unresolvable deadlock. I would rate that as pretty unlikely, though. Locking is a pretty fundamental part of Postgres that gets a lot of testing. -- Bill Moran
