Re: Testing autovacuum wraparound (including failsafe)

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Ian Lawrence Barwick <barwick(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Anastasia Lubennikova <lubennikovaav(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Testing autovacuum wraparound (including failsafe)
Date: 2023-03-09 06:46:53
Message-ID: ZAmA3V9J7nPVvNoo@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Mar 07, 2023 at 09:21:00PM -0800, Peter Geoghegan wrote:
> Surely your tap test should be using single user mode? Perhaps you
> missed the obnoxious HINT, that's part of the WARNING that the test
> parses? ;-)

I may be missing something, but you cannot use directly a "postgres"
command in a TAP test, can you? See 1a9d802, that has fixed a problem
when TAP tests run with a privileged account on Windows.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2023-03-09 06:51:05 Re: [PoC] Improve dead tuple storage for lazy vacuum
Previous Message Michael Paquier 2023-03-09 06:37:21 Re: Add pg_walinspect function with block info columns