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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Cherio <cherio(at)gmail(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
Date: 2023-02-27 18:00:01
Message-ID: 391334.1677520801@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Cherio <cherio(at)gmail(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Cherio 2023-02-27 18:06:45 Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
Previous Message Cherio 2023-02-27 17:54:51 Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM