Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
Date
Msg-id 391334.1677520801@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM  (Cherio <cherio@gmail.com>)
Responses Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM  (Cherio <cherio@gmail.com>)
List pgsql-bugs
Cherio <cherio@gmail.com> writes:
> I just realized that the ramifications of this change go further than just
> VACUUM related statements in the scripts. Assume 2 scripts

> UPDATE tableA
> UPDATE tableB

> and

> UPDATE tableA
> UPDATE tableB

> Before the change they could run in parallel without issues. After the
> change this will cause one of the queries to fail due to transaction locks.

Uh ... really?  Please provide evidence.  AFAIK this set of changes
only affects commands that are meant to not run inside tranaction blocks.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Cherio
Date:
Subject: Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
Next
From: Cherio
Date:
Subject: Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM