Re: Decoding of (nearly) empty transactions and regression tests - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Decoding of (nearly) empty transactions and regression tests
Date
Msg-id 8413.1404054519@sss.pgh.pa.us
Whole thread Raw
In response to Re: Decoding of (nearly) empty transactions and regression tests  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: Decoding of (nearly) empty transactions and regression tests  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
Andres Freund <andres@2ndquadrant.com> writes:
> On 2014-06-29 10:36:22 -0400, Tom Lane wrote:
>> You mean disable autovac only in the contrib/test_decoding check run,
>> right?  That's probably OK since it's tested in the main regression
>> runs.

> Actually I'd not even though of that, but just of disabling it on
> relations with relevant amounts of changes in the test_decoding
> tests. That way it'd work even when run against an existing server (via
> installcheck-force) which I found useful during development.

I think that a change that affects the behavior in any other test runs is
not acceptable.  Our testing of autovac is weaker than I'd like already
(since the main regression runs are designed to not show visible changes
when it runs).  I don't want it being turned off elsewhere for the benefit
of this test.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: PostgreSQL for VAX on NetBSD/OpenBSD
Next
From: Andres Freund
Date:
Subject: Re: Decoding of (nearly) empty transactions and regression tests