pgsql: Try to harden insert-conflict-specconflict against autovacuum.

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Try to harden insert-conflict-specconflict against autovacuum.
Date: 2020-02-12 05:19:01
Message-ID: E1j1kQP-0005c9-Ed@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Try to harden insert-conflict-specconflict against autovacuum.

Looks like guaibasaurus had a autovacuum running during the
controller_print_speculative_locks step (just added in
43e08419708). Which does indeed seem quite possible.

Avoid the problem by only looking for the backends participating in
the test.

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/997563dfcb2501a7a199589cd6f15f2bb8af3d04

Modified Files
--------------
.../isolation/expected/insert-conflict-specconflict.out | 15 ++++++++++++---
.../isolation/specs/insert-conflict-specconflict.spec | 5 ++++-
2 files changed, 16 insertions(+), 4 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Fujii Masao 2020-02-12 09:11:06 Re: pgsql: walreceiver uses a temporary replication slot by default
Previous Message Michael Paquier 2020-02-12 05:13:06 Re: pgsql: walreceiver uses a temporary replication slot by default