Re: gcov coverage data not full with immediate stop

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Alexander Lakhin <exclusion(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: gcov coverage data not full with immediate stop
Date: 2020-05-13 22:59:08
Message-ID: CAH2-Wz=X86EQrpOKpR_V2X3UdigHFTrREbwNwc9pzfrRWk+v+g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, May 12, 2020 at 10:10 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2020-05-13 23:06:07 Re: Concurrency bug in amcheck
Previous Message Peter Geoghegan 2020-05-13 22:55:47 Re: Index Skip Scan