Re: [COMMITTERS] pgsql: Improve pg_dump regression tests and code coverage

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Improve pg_dump regression tests and code coverage
Date: 2017-03-20 14:35:15
Message-ID: 20170320143515.GM9812@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Robert,

* Robert Haas (robertmhaas(at)gmail(dot)com) wrote:
> I'm glad that you are working on fixing
> pg_dump bugs and improving test coverage, but my gladness about that
> does not extend to thinking that the processes which other people
> follow for their work should be waived for yours. Sorry.

To be clear, I am not asking for any kind of special exception for
myself.

I continue to be of the opinion that this entire discussion is quite
flipped from how we really should be running things- adding regression
tests to improve code coverage, particularly when they're simply adding
to the existing structure for those tests, should be strongly encouraged
both before and after feature-freeze.

Thanks.

Stephen

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2017-03-20 14:42:35 Re: Re: [COMMITTERS] pgsql: Improve pg_dump regression tests and code coverage
Previous Message Robert Haas 2017-03-20 14:24:22 Re: [COMMITTERS] pgsql: Improve pg_dump regression tests and code coverage

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2017-03-20 14:35:16 Our feature change policy
Previous Message Robert Haas 2017-03-20 14:28:30 Re: free space map and visibility map