Re: issue with track_commit_timestamp and server restart

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Álvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Subject: Re: issue with track_commit_timestamp and server restart
Date: 2016-10-24 05:04:17
Message-ID: CAB7nPqQe1_=oVvVzRZgYMUBo2QPQJVSutOSs5YoRhZPnewK+Jg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

(thread hijacking)

On Mon, Oct 24, 2016 at 1:58 PM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
> To save time running the recovery suite, just
>
> rm src/test/recovery/00[0-8]*.pl
>
> (It'd be nice to have a prove_check target to run just one test file).

Agreed! Or multiple chosen files. I usually remove those files
manually from time to time when working on a fix just to run one
dedicated test repeatedly.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2016-10-24 05:08:16 Re: issue with track_commit_timestamp and server restart
Previous Message Craig Ringer 2016-10-24 04:58:20 Re: issue with track_commit_timestamp and server restart