Re: gcov coverage data not full with immediate stop - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: gcov coverage data not full with immediate stop
Date
Msg-id CAH2-Wz=X86EQrpOKpR_V2X3UdigHFTrREbwNwc9pzfrRWk+v+g@mail.gmail.com
Whole thread Raw
In response to Re: gcov coverage data not full with immediate stop  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, May 12, 2020 at 10:10 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > Can that easily be accommodated?
>
> There's no real lead time needed AFAICS: when we are ready to branch,
> we can just do it.  So sure, let's wait till the end of May to decide.
> If things look bad then, we could reconsider again mid-June.

Great. Let's review it at the end of May, before actually branching.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Index Skip Scan
Next
From: Peter Geoghegan
Date:
Subject: Re: Concurrency bug in amcheck