Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM

Cherio <cherio@gmail.com> writes:
> The second script should have tables used in the reversed order:
> UPDATE tableA
> UPDATE tableB

> and

> UPDATE tableB
> UPDATE tableA

> Since they will run in individual transactions tableA gets locked by the
> 1st script and tableB by the 2nd; as execution flow proceeds to the next
> update in each script, those tables would be locked in separate
> transactions.

I think you are working with a completely wrong mental model of what
this change did.  It will not affect a pipeline that doesn't contain
any VACUUM, ANALYZE, or similar maintenance commands.

            regards, tom lane